Re: problem unwinding past pthread_cond_wait() on x86 RedHat 9.0

[Andrew Cagney <ac131313 at redhat dot 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

Joel, what happens if you type:

(gdb) x/i 0xffffe002

Andrew

> 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.