Re: RFC: Fix gdb 5.1 for Linuxthreads

[Duncan Palmer <duncan.palmer@s3group.com>]

"H . J . Lu" wrote:
> 
> On Tue, Sep 18, 2001 at 01:55:55PM -0700, H . J . Lu wrote:
> > On Mon, Sep 17, 2001 at 07:13:57PM -0700, H . J . Lu wrote:
> > > >
> > > > The more I looked at it, the more borken gdb is with linuxthreads:
> > > >
> > > > # gcc -g ex11.c -lpthread -lrt -D_GNU_SOURCE -static
> > > > # a.out
> > > > # gdb a.out
> > > > ...
> > > > (gdb) att 14226
> > > > Attaching to program: /home/hjl/bugs/gdb/thread/a.out, process 14226
> > > > ...
> > > > lin-lwp.c:620: gdb-internal-error: stop_wait_callback: Assertion `pid ==
> > > > GET_LWP (lp->ptid)' failed.
> > > > An internal GDB error was detected.  This may make further
> > >
> > > It looks like with gdb 5.1, I have to attach the very first thread. Is
> > > that documented anywhere? Shouldn't gdb find the very first thread
> > > and attach it for me?

I've just given your patch a try, and it works well for me. I have
another thread related problem with gdb 5.1 however - if i start my
application from within gdb, or attach to any threads of the process,
'info threads' gives me back nothing despite the fact that there are
quite a few threads running - this works fine when i use the version of
gdb 4.18 that comes with Mandrake (i assume its the same as comes with
RedHat, but i'm not sure if it has thread related patches applied or
not). 

I'm using glibc 2.1.3 and libpthreads 0.8 on x86

Dunk.