From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: redhat.com, ip: 209.132.183.28, mailfrom: lersek@redhat.com) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by groups.io with SMTP; Tue, 07 May 2019 04:49:36 -0700 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6C78F307D91F; Tue, 7 May 2019 11:49:35 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-152.rdu2.redhat.com [10.10.120.152]) by smtp.corp.redhat.com (Postfix) with ESMTP id 54883611D4; Tue, 7 May 2019 11:49:34 +0000 (UTC) Subject: Re: [edk2-devel] Adding DebugPkg to the main edk2 repo To: devel@edk2.groups.io, ryszard.knop@linux.intel.com, michael.d.kinney@intel.com, "rebecca@bluestop.org" References: <19e9d54a-575a-ee5e-8039-900f466d473d@bluestop.org> <1a7c397b-71c5-84e0-39e6-bcad8b847392@linux.intel.com> From: "Laszlo Ersek" Message-ID: <8354bb89-ce10-e45a-244b-5ae4c004b5e4@redhat.com> Date: Tue, 7 May 2019 13:49:33 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <1a7c397b-71c5-84e0-39e6-bcad8b847392@linux.intel.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.48]); Tue, 07 May 2019 11:49:35 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05/07/19 10:59, Ryszard Knop wrote: > Hi Mike, >=20 > 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. >=20 > 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. >=20 > Thanks, Richard >=20 > On 2019-05-07 8:13, Michael D Kinney wrote: >> Hi Rebecca, >> >> This content does not look OVMF specific. >> >> Does it depend on QEMU?=C2=A0 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 t= he 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?=C2=A0 Not sure >> why the extra module is required.=C2=A0 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. >>> >>> >>> --=20 >>> Rebecca Cran >>> >>> >>> >> >> >> >=20 >=20 >=20