From: "andrzej zaborowski" <balrog@zabor.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Debugging with paging enabled
Date: Fri, 10 Nov 2006 13:14:12 +0000 [thread overview]
Message-ID: <fb249edb0611100514k30f6dcebs802f57c33a96fbd3@mail.gmail.com> (raw)
In-Reply-To: <816057700.20061109005729@kilgus.net>
On 08/11/06, Marcel Kilgus <qemu@mail.kilgus.net> wrote:
> > Correct. It doesn't know anything at all about i386 segmentation.
>
> Well, that explains it then, I guess. In that case I don't really see
> a clean solution for it.
If I understand the problem, the clean solution is having the
debugging symbols at the right addresses: in code that runs with
paging enabled symbols should be at their virtual addresses and the
other symbols at physical addresses. Since the period from start to
enabling paging is usually short, I think most kernels generate only
virtual addresses for the symbols. I don't remember the ld option to
move text-base to the right address but see Linux. GDB works perfectly
for it. It doesn't need to know about segmentation if your symbols are
correct.
--
balrog 2oo6
next prev parent reply other threads:[~2006-11-10 13:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 2:30 [Qemu-devel] Debugging with paging enabled Marcel Kilgus
2006-11-08 21:13 ` [Qemu-devel] " Marcel Kilgus
2006-11-08 22:15 ` Fabrice Bellard
2006-11-08 23:33 ` Marcel Kilgus
2006-11-08 23:42 ` Daniel Jacobowitz
2006-11-08 23:57 ` Marcel Kilgus
2006-11-09 2:24 ` Daniel Jacobowitz
2006-11-10 13:14 ` andrzej zaborowski [this message]
2006-11-10 14:31 ` Marcel Kilgus
2006-11-10 15:56 ` Paul Brook
2006-11-10 16:14 ` Marcel Kilgus
2006-11-10 17:10 ` Daniel Jacobowitz
2006-11-10 19:01 ` Marcel Kilgus
2006-11-10 19:07 ` 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=fb249edb0611100514k30f6dcebs802f57c33a96fbd3@mail.gmail.com \
--to=balrog@zabor.org \
--cc=balrogg@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).