From: Rebecca Cran <rebecca@bluestop.org>
To: Johannes Swoboda <johannes.swoboda@student.tuwien.ac.at>,
"Palmer, Thomas" <thomas.palmer@hpe.com>,
Laszlo Ersek <lersek@redhat.com>
Cc: Michael Kinney <michael.d.kinney@intel.com>,
edk2-devel@lists.01.org, clemens.hlauschek@inso.tuwien.ac.at
Subject: Re: gdb reload-uefi missing EFI_SYSTEM_TABLE_POINTER [was: Source code debugging of OVMF]
Date: Fri, 20 Apr 2018 10:49:39 -0600 [thread overview]
Message-ID: <01bebb35-5a6b-2b6c-5297-c8bd5953c7bc@bluestop.org> (raw)
In-Reply-To: <e21bcafbe7a694d1114fb19cc8f8d672@student.tuwien.ac.at>
On 04/20/18 10:38, Johannes Swoboda wrote:
> Hello again,
>
> Thank you again for taking the time to help me with this.
>
> On 2018-04-20 17:58, Palmer, Thomas wrote:
>> Also, did you start qemu with the "-s" option before you started gdb?
>
> Unfortunately, I start qemu with -s -S; then, I attach gdb. I know the
> attaching works because I gdb accepts the continue command which
> instructs qemu to begin execution of the virtual machine.
> The source [...]/gdb_uefi.py command seems to work find, but reload-efi
> -o [...]/DEBUG/GdbSyms.dll throws the error "No type named
> EFI_SYSTEM_TABLE_POINTER".
...
> Do you have any other suggestions?
I'm not sure things have loaded to the point necessary by then. I'd
suggest putting a call to CpuDeadLoop() someplace maybe near where you
want to start debugging. Then once attached to dbg, set the `Index`
variable to 1 to continue.
--
Rebecca
next prev parent reply other threads:[~2018-04-20 16:49 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
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 [this message]
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=01bebb35-5a6b-2b6c-5297-c8bd5953c7bc@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