From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Joel Brobecker <brobecker@gnat.com>,
Andrew Cagney <ac131313@redhat.com>,
gdb-patches@sources.redhat.com
Subject: Re: problem unwinding past pthread_cond_wait() on x86 RedHat 9.0
Date: Tue, 14 Oct 2003 16:15:00 -0000 [thread overview]
Message-ID: <3F8C2139.3040904@redhat.com> (raw)
In-Reply-To: <20031014155211.GB10669@nevyn.them.org>
> On Tue, Oct 14, 2003 at 08:46:49AM -0700, Joel Brobecker wrote:
>
>> > Joel, what happens if you type:
>> >
>> > (gdb) x/i 0xffffe002
>
>>
>> Something like "Cannot read memory at 0xffffe002" (already tried it :-).
>> What is this address, BTW. I always wondered... Kernel code? Special
>> address?
>
>
> Search for "vsyscall DSO" in the gdb@ archives to learn more than you
> ever wanted to know :) Patches to fully support it are still pending.
No.
No matter how much you patch GDB, GDB isn't going to dig itself out of
thishole. It's not able to access the code/data/whatever at that
address so it's never going to correctly unwind from it.
Kernel bug - incomplete functionality.
Andrew
next prev parent reply other threads:[~2003-10-14 16:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 5:42 Joel Brobecker
2003-10-14 12:57 ` Daniel Jacobowitz
2003-10-14 15:24 ` Andrew Cagney
2003-10-14 15:46 ` Joel Brobecker
2003-10-14 15:52 ` Daniel Jacobowitz
2003-10-14 16:15 ` Andrew Cagney [this message]
2003-10-14 16:18 ` Daniel Jacobowitz
2003-10-14 16:19 ` Joel Brobecker
2003-10-14 15:53 ` Elena Zannoni
2003-10-14 15:58 ` Joel Brobecker
2003-10-14 16:02 ` Daniel Jacobowitz
2003-10-14 16:21 ` Joel Brobecker
2003-10-16 22:13 ` Richard Henderson
2003-10-15 19:34 ` Mark Kettenis
2003-10-23 1:07 ` Joel Brobecker
2003-10-23 2:41 ` 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=3F8C2139.3040904@redhat.com \
--to=ac131313@redhat.com \
--cc=brobecker@gnat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/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