Re: [edk2-devel] Adding DebugPkg to the main edk2 repo

["Ryszard Knop" <ryszard.knop@linux.intel.com>]

Hi Mike,

GdbSyms can be built separately from the debugged image. It produces a
DLL file to load while starting GDB so that it properly detects the
target once connected. The associated gdb_uefi.py script loads it with
symbol-file to get some info required to find the system table, etc
(see search_est function).

I'm using this script (with QEMU only, not sure about other platforms,
but could work I guess?) and have a Python 3 port if someone needs it.

Thanks, Richard

On 2019-05-07 8:13, Michael D Kinney wrote:
> Hi Rebecca,
>
> This content does not look OVMF specific.
>
> Does it depend on QEMU?  Or would this
> Potentially work on any target that supports
> gdb?
>
> How about adding to SourceLevelDebugPkg as
> an another method to load symbols?  Not sure
> why the extra module is required.  The Debug
> Image Info Table is defined to be on a 4MB
> boundary and can be found with a search.
>
> Mike
>
>> -----Original Message-----
>> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io]
>> On Behalf Of rebecca@bluestop.org
>> Sent: Monday, May 6, 2019 7:04 PM
>> To: devel@edk2.groups.io
>> Subject: [edk2-devel] Adding DebugPkg to the main edk2
>> repo
>>
>> I think this has been discussed previously, but since
>> time has passed
>> I'd like to check again: is there any possibility of
>> having the DebugPkg
>> from https://github.com/andreiw/andreiw-
>> wip/tree/master/uefi/DebugPkg
>> added to the main edk2 repo in some way (perhaps not as
>> DebugPkg, but
>> renamed/reorganized/integrated)?
>>
>>
>> It seems such a useful addition for debugging UEFI code
>> running under
>> OVMF that it would be nice to have it somewhere it has
>> less chance of
>> bitrotting.
>>
>>
>> --
>> Rebecca Cran
>>
>>
>>
>
> 
>