This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: unable to debug statically linked program with linux threads
- From: "Ajay Patel" <ajayp at kymasys dot com>
- To: Daniel Jacobowitz <drow at false dot org>,Ajay Patel <ajayp at kymasys dot com>,gdb at sources dot redhat dot com
- Date: Thu, 17 Mar 2005 15:59:12 -0800
- Subject: Re: unable to debug statically linked program with linux threads
Daniel,
I checked out gdb from CVS head and applied this
"http://sourceware.org/ml/gdb-patches/2004-12/msg00240.html";
patch.
But still no thread commands.
Thanks for your help.
Ajay
> On Thu, Mar 17, 2005 at 02:06:57PM -0800, Ajay Patel wrote:
> >
> > Hi,
> > I have a FC3 based i686 machine with gdb version 6.1.
> > I got a simple threaded program from one BSD. (program attached)
> >
> > With dynamic linking (linux threads), I can run
> > the program under gdb without a problem.
> > All thread related commands seems to work properly.
> >
> > With static linking, when I run this program under
> > gdb, first I get
> > "Program received signal SIG32/SIG33 Real-time event 32/32".
> > I avoid this problem by
> > "handle SIG32/SIG33 pass nostop noprint".
> >
> > However none of the thread related command works.
> >
> > Any suggestion?
>
> There's a patch in the gdb-patches archive for this. I'll go ping
> it... it applies to CVS HEAD GDB.
>
>
> --
> Daniel Jacobowitz
> CodeSourcery, LLC
>
>