From: "Ajay Patel" <ajayp@kymasys.com>
To: Daniel Jacobowitz <drow@false.org>,Ajay Patel
<ajayp@kymasys.com>,gdb@sources.redhat.com
Subject: Re: unable to debug statically linked program with linux threads
Date: Thu, 17 Mar 2005 23:59:00 -0000 [thread overview]
Message-ID: <1111103952.21230@horse.he.net> (raw)
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
>
>
next reply other threads:[~2005-03-17 23:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 23:59 Ajay Patel [this message]
2005-03-18 2:47 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2005-03-18 23:53 Ajay Patel
2005-03-17 22:07 Ajay Patel
2005-03-17 22:13 ` Daniel Jacobowitz
2005-03-17 22:19 ` Eric Desjardins
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=1111103952.21230@horse.he.net \
--to=ajayp@kymasys.com \
--cc=drow@false.org \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).