From: "Adnan Khaleel" <adnan@khaleel.us>
To: Mulyadi Santosa <mulyadi.santosa@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Howto debug boot device not showing up in bios
Date: Tue, 10 May 2011 14:28:01 -0500 [thread overview]
Message-ID: <20110510192801.6897dd2d@shadowfax.no-ip.com> (raw)
In-Reply-To: BANLkTinhP_EVrQ+u7qhY3gMzeNimiEZX0w@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
I meant what is the best way to debug the qemu and seabios interaction, I don't necessarily want to inspect instructions but rather just the function calls and trace the process so I can compare it for another case that isn't working.
AK
_____
From: Mulyadi Santosa [mailto:mulyadi.santosa@gmail.com]
To: adnan@khaleel.us
Cc: qemu-devel@nongnu.org
Sent: Tue, 10 May 2011 01:49:31 -0500
Subject: Re: [Qemu-devel] Howto debug boot device not showing up in bios
Hi....
On Tue, May 10, 2011 at 05:24, Adnan Khaleel <adnan@khaleel.us> wrote:
> Can somebody give me some pointers on what the best way to debug the boot
> process in Qemu and seabios?
At first, I guess "-s" a.k.a qemu gdb stub of Qemu could help
you...but uhm, on a second thought, I think it is the qemu itself that
you need to run under Qemu...
regarding seabios code, i have no idea how to debug that... is it a
binary blob only?
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
[-- Attachment #2: Type: text/html, Size: 1655 bytes --]
next reply other threads:[~2011-05-10 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 19:28 Adnan Khaleel [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-09 22:24 [Qemu-devel] Howto debug boot device not showing up in bios Adnan Khaleel
2011-05-10 6:49 ` Mulyadi Santosa
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-all 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=20110510192801.6897dd2d@shadowfax.no-ip.com \
--to=adnan@khaleel.us \
--cc=mulyadi.santosa@gmail.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).