public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Bruce Cran <bruce@cran.org.uk>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>,
	edk2-devel@ml01.01.org, Liming Gao <liming.gao@intel.com>,
	"Jordan Justen (Intel address)" <jordan.l.justen@intel.com>,
	andrey.warkentin@gmail.com
Subject: Re: [Patch] BaseTools: support the NOOPT target with the GCC tool chains
Date: Sun, 2 Oct 2016 19:45:28 -0600	[thread overview]
Message-ID: <d66e2452-f46d-31d1-3841-ec29efd5f223@cran.org.uk> (raw)
In-Reply-To: <5abd5d33-2301-e32f-12ed-2154748a6bee@redhat.com>

(cc'ing Andrei Warkentin)

On 9/30/2016 4:11 AM, Laszlo Ersek wrote:
> Can you please test this in the environment where you wanted to use it
> originally? (I assume you were using some kind of source level debugging.)
>
> For that, you'll probably have to add NOOPT to BUILD_TARGETS in the
> OvmfPkg/OvmfPkg*.dsc files. If you do that and everything works fine for
> you, I'd appreciate if you could also submit the OvmfPkg patch to the list.

The patch looks good, but unfortunately for some reason it breaks 
debugging using Andrei's gdb_uefi.py script: loading symbols fails:

The target architecture is assumed to be i386:x86-64:intel
0x000000007e65dec8 in ?? ()
Python Exception <class 'gdb.error'> No type named 
EFI_SYSTEM_TABLE_POINTER.:
/home/bcran/.gdbinit:8: Error in sourced command file:
Error occurred in Python command: No type named EFI_SYSTEM_TABLE_POINTER.

I've verified that a DEBUG build with the same git checkout does still 
work. I've looked through OvmfX64.dsc and couldn't see anything that 
depends on DEBUG that would be omitting stuff for NOOPT, so I'm stuck.

-- 
Bruce


  reply	other threads:[~2016-10-03  1:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30  7:44 [Patch] BaseTools: support the NOOPT target with the GCC tool chains Yonghong Zhu
2016-09-30 10:11 ` Laszlo Ersek
2016-10-03  1:45   ` Bruce Cran [this message]
2016-10-03  8:59     ` Laszlo Ersek
2016-10-03 16:02       ` Bruce Cran
2016-10-03 16:09         ` Laszlo Ersek
2016-10-03 16:13           ` Bruce Cran
2016-10-03 16:53             ` Laszlo Ersek
2016-10-05  1:32               ` Zhu, Yonghong
2016-10-03 16:11 ` Bruce Cran

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d66e2452-f46d-31d1-3841-ec29efd5f223@cran.org.uk \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox