From: Daniel Jacobowitz <drow@false.org>
To: jo@atsresults.com
Cc: gdb@sources.redhat.com
Subject: Re: Can't debug Threaded application
Date: Mon, 29 Aug 2005 16:11:00 -0000 [thread overview]
Message-ID: <20050829161133.GA27388@nevyn.them.org> (raw)
In-Reply-To: <1125331733.43133315376a9@webmail.atsresults.com>
On Mon, Aug 29, 2005 at 12:08:53PM -0400, jo@atsresults.com wrote:
> Does no one have answer to this problem?
>
> Is GDB useless for threaded applications now?
Of course not. No one's responded because no one has advice that you
can't find in the list archives. This almost always means something is
broken on your installation. You may want to report it to Trustix,
since that's your distribution.
> > Is there any work arounds for this bug? I have tried this:
> >
> > (gdb)> set auto-solib-add 0
> > (gdb)> handle S1G32 nostop noprint
These will definitely not help anything. I wish people would stop
suggesting them.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-08-29 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 20:18 jo
2005-08-29 16:09 ` jo
2005-08-29 16:11 ` Daniel Jacobowitz [this message]
2005-08-29 17:06 ` Russell Shaw
2005-08-29 17:08 ` Daniel Jacobowitz
2005-08-29 17:19 ` Russell Shaw
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=20050829161133.GA27388@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jo@atsresults.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