From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: thread apply all - not working?
Date: Fri, 27 May 2005 19:30:00 -0000 [thread overview]
Message-ID: <20050527193022.GA19269@nevyn.them.org> (raw)
In-Reply-To: <20050527192506.GE59006@keyslapper.net>
On Fri, May 27, 2005 at 03:25:06PM -0400, Louis LeBlanc wrote:
> On 05/27/05 03:15 PM, Daniel Jacobowitz sat at the `puter and typed:
> > On Fri, May 27, 2005 at 02:46:46PM -0400, Louis LeBlanc wrote:
> > > I'm having trouble getting stack traces on all threads from a core file.
> > >
> > > I was under the impression that "thread apply all bt" should get it, but
> > > I only get the last thread.
> > >
> > > I am using GNU gdb 6.3.0.20050516-cvs on Solaris. The core was
> > > generated by an app built with gcc 3.3.
> > >
> > > Am I missing something?
> >
> > Does info threads show multiple threads? If not, either the core dump
> > only contains one thread, or GDB does not know how to extract threads
> > from a core dump on Solaris - I think this used to work, but I don't
> > know if it has been tried lately.
>
>
> Of course, there are 104 threads in this particular core, and the app is
> configured to run up to 500. The command I am trying gives me thread
> 104, but no others. I am able to get stack traces if I explicity select
> them one at a time, but with up to 500 threads, you can imagine how much
> fun this will be . . .
OK, that's progress. Please show me the entire output of 'thread apply all
bt'.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-27 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 18:45 Louis LeBlanc
2005-05-27 19:15 ` Daniel Jacobowitz
2005-05-27 19:24 ` Louis LeBlanc
2005-05-27 19:30 ` Daniel Jacobowitz [this message]
2005-05-27 19:49 ` Louis LeBlanc
2005-05-27 19:57 ` Daniel Jacobowitz
2005-05-27 20:13 ` Louis LeBlanc
2005-05-28 0:12 ` Daniel Jacobowitz
2005-05-27 20:18 ` Louis LeBlanc
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=20050527193022.GA19269@nevyn.them.org \
--to=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