From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: problem unwinding past pthread_cond_wait() on x86 RedHat 9.0
Date: Tue, 14 Oct 2003 12:57:00 -0000 [thread overview]
Message-ID: <20031014125731.GA14097@nevyn.them.org> (raw)
In-Reply-To: <20031014054225.GB919@gnat.com>
On Mon, Oct 13, 2003 at 10:42:25PM -0700, Joel Brobecker wrote:
> We now basically get almost nothing:
>
> #0 0xffffe002 in ?? ()
> #1 0x4002d379 in pthread_cond_wait@@GLIBC_2.3.2 ()
> from /lib/tls/libpthread.so.0
That's NPTL. Are you sure you understand the problem right - I don't
have RH9's glibc here, only Rawhide's, but there's CFI for
pthread_cond_wait in Rawhide.
So anyway this _will_ go away someday.
> The problem I am now trying to solve is the following: How can we fix
> the i386 unwinder to be smart enough to handle this wicked function?
> Is this even possible? The only possibility I see right now is with
> dwarf2 CFI, but then the problem I foresee is that we can not help
> the people using the stock RH9. If the only hope is with CFI, then
> they will have to update their pthread library...
You really can't unwind past this sort of thing without either debug
info or frame pointers. How did it work in 5.3? I'm assuming dumb
luck, we unwound 0xfffffe02 wrong.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-10-14 12:57 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 [this message]
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
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=20031014125731.GA14097@nevyn.them.org \
--to=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