public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, ryszard.knop@linux.intel.com,
	michael.d.kinney@intel.com,
	"rebecca@bluestop.org" <rebecca@bluestop.org>
Subject: Re: [edk2-devel] Adding DebugPkg to the main edk2 repo
Date: Tue, 7 May 2019 13:49:33 +0200	[thread overview]
Message-ID: <8354bb89-ce10-e45a-244b-5ae4c004b5e4@redhat.com> (raw)
In-Reply-To: <1a7c397b-71c5-84e0-39e6-bcad8b847392@linux.intel.com>

On 05/07/19 10:59, Ryszard Knop wrote:
> 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).

Yes, that function performs the 4MB-aligned search that Mike mentioned.

> 
> 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?

I'd expect it to interoperate with any gdb server implementation.

Whenever I use DebugPkg, to connect to a running QEMU instance, I launch the following gdb scriptlet (with "gdb -x") from a file:

set height 0
set architecture i386:x86-64:intel
target remote localhost:1234
source .../DebugPkg/Scripts/gdb_uefi.py
reload-uefi -o .../Build/Ovmf3264/NOOPT_GCC48/X64/DebugPkg/GdbSyms/GdbSyms/DEBUG/GdbSyms.dll

Thanks
Laszlo

>>
>> 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
>>>
>>>
>>>
>>
>>
>>
> 
> 
> 


  reply	other threads:[~2019-05-07 11:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07  2:04 Adding DebugPkg to the main edk2 repo rebecca
2019-05-07  6:13 ` [edk2-devel] " Michael D Kinney
2019-05-07  8:59   ` Ryszard Knop
2019-05-07 11:49     ` Laszlo Ersek [this message]
2019-05-07 15:28       ` rebecca

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=8354bb89-ce10-e45a-244b-5ae4c004b5e4@redhat.com \
    --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