From: "Mulyadi Santosa" <mulyadi.santosa@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Debugging vmlinux with qemu and gdb. Unable to step, next, print or to get any information..
Date: Fri, 9 May 2008 09:31:24 +0700 [thread overview]
Message-ID: <f284c33d0805081931u72ca5b3fr80bf4c9b1721bc37@mail.gmail.com> (raw)
In-Reply-To: <824D057211107844BA95DB341B4BF12E01139BF2@hanvsmail04.eu.thmulti.com>
Hi...
On Thu, May 8, 2008 at 2:53 PM, Keilhau Timo ( Student )
<timo.keilhau.student@thomson.net> wrote:
> Ive compiled the 2.6.25 kernel on guest with:
> [*] Compile the kernel with frame pointers
> [*] Compile the kernel with debug info
> additionally CFLAGS="-g3 -ggdb"
You meant -O3? well, IMO, you don't need -O at all. AFAIK mixing -g or
-ggdb with -O{1,2,3} is a bad thing, since it will render the DWARF
information inside the ELF file (in this case, the vmlinux)
inconsistent with the runtime context (line number, current EIP
correlated with break points).
Of course, this assume that there is no bugs while Qemu inspect and
found that it must pause at certain address... I believe Jasson Wessel
had squashed all that kind of bugs in the past.
regards,
Mulyadi.
next prev parent reply other threads:[~2008-05-09 2:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 7:53 [Qemu-devel] Debugging vmlinux with qemu and gdb. Unable to step, next, print or to get any information Keilhau Timo ( Student )
2008-05-08 8:28 ` [Qemu-devel] " Jan Kiszka
2008-05-08 9:09 ` Keilhau Timo ( Student )
2008-05-08 18:39 ` Jan Kiszka
2008-05-09 2:31 ` Mulyadi Santosa [this message]
2008-05-09 4:39 ` [Qemu-devel] " Jason Wessel
2008-05-09 7:23 ` Mulyadi Santosa
2008-05-09 8:29 ` Jan Kiszka
2008-05-09 9:03 ` Keilhau Timo ( Student )
2008-05-09 10:03 ` Mulyadi Santosa
2008-05-09 8:38 ` Edgar E. Iglesias
2008-05-09 14:40 ` Daniel Jacobowitz
2008-05-09 14:47 ` Jason Wessel
2008-05-09 16:39 ` Daniel Jacobowitz
2008-05-12 9:41 ` Edgar E. Iglesias
2008-05-12 12:51 ` Jason Wessel
2008-05-12 13:30 ` Edgar E. Iglesias
2008-05-12 14:02 ` Edgar E. Iglesias
2008-05-12 14:31 ` Jason Wessel
2008-05-12 14:33 ` Paul Brook
2008-05-12 14:47 ` Edgar E. Iglesias
2008-05-12 14:48 ` Jason Wessel
2008-05-12 12:51 ` Daniel Jacobowitz
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=f284c33d0805081931u72ca5b3fr80bf4c9b1721bc37@mail.gmail.com \
--to=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).