public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"rebecca@bluestop.org" <rebecca@bluestop.org>
Subject: Re: [edk2-devel] Adding DebugPkg to the main edk2 repo
Date: Tue, 7 May 2019 06:13:48 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B9CA3CC1@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <19e9d54a-575a-ee5e-8039-900f466d473d@bluestop.org>

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


  reply	other threads:[~2019-05-07  6:14 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 ` Michael D Kinney [this message]
2019-05-07  8:59   ` [edk2-devel] " Ryszard Knop
2019-05-07 11:49     ` Laszlo Ersek
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=E92EE9817A31E24EB0585FDF735412F5B9CA3CC1@ORSMSX113.amr.corp.intel.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