public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Rebecca Cran <rebecca@bluestop.org>
To: Laszlo Ersek <lersek@redhat.com>,
	Johannes Swoboda <johannes.swoboda@student.tuwien.ac.at>
Cc: Michael Kinney <michael.d.kinney@intel.com>,
	edk2-devel@lists.01.org, clemens.hlauschek@inso.tuwien.ac.at
Subject: Re: Source code debugging of OVMF
Date: Mon, 16 Apr 2018 12:25:44 -0600	[thread overview]
Message-ID: <e5f6c619-9db3-9ae4-089a-456c50273fab@bluestop.org> (raw)
In-Reply-To: <12fe2332-c864-60e1-4f12-280e9939449f@redhat.com>

On 04/16/18 10:13, Laszlo Ersek wrote:

> Here's another thread that you might find useful:
> 
> http://edk2-devel.narkive.com/6BRVus92/qestion-about-how-to-debug-ovmf-on-qemu

I should get my Phabricator wiki running again, which has a
nicely-formatted version of that - I haven't set it up again after
moving systems.

-- 
Rebecca


  parent reply	other threads:[~2018-04-16 18:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 11:09 Source code debugging of OVMF Johannes Swoboda
2018-04-16 15:26 ` Richardson, Brian
2018-04-16 16:03   ` Blibbet
2018-04-20 13:32   ` Johannes Swoboda
2018-04-16 16:13 ` Laszlo Ersek
2018-04-16 16:53   ` Palmer, Thomas
2018-04-16 18:25   ` Rebecca Cran [this message]
2018-04-16 19:57     ` Laszlo Ersek
2018-04-19  2:46     ` Rebecca Cran
2018-04-19  8:41       ` Laszlo Ersek
2018-04-20 14:54       ` gdb reload-uefi missing EFI_SYSTEM_TABLE_POINTER [was: Source code debugging of OVMF] Johannes Swoboda
2018-04-20 15:20         ` Laszlo Ersek
2018-04-20 15:58           ` Palmer, Thomas
2018-04-20 16:38             ` Johannes Swoboda
2018-04-20 16:45               ` Palmer, Thomas
2018-04-20 16:49               ` Rebecca Cran
2018-04-24  2:13         ` Gary Lin
2018-05-24 12:52           ` Johannes Swoboda

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=e5f6c619-9db3-9ae4-089a-456c50273fab@bluestop.org \
    --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