Re: [Patch] BaseTools: support the NOOPT target with the GCC tool chains

[Laszlo Ersek <lersek@redhat.com>]

On 10/03/16 03:45, Bruce Cran wrote:
> (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.
> 

Can you compare "DEBUG/GdbSyms.dll" with "NOOPT/GdbSyms.dll", just
visually, using "nm" and/or "readelf"? Something might stand out.

Thanks
Laszlo