From: "John Chenoweth" <jchenowe@bigpond.net.au>
To: <gdb@sourceware.org>
Subject: RE: Solaris Core file analysis
Date: Fri, 02 Nov 2007 07:41:00 -0000 [thread overview]
Message-ID: <001a01c81d23$b82ac250$9400a8c0@zaphod> (raw)
In-Reply-To: <001b01c81ac7$033ea3b0$9400a8c0@zaphod>
Can anyone help me with that below?
>John Chenoweth
>* +61 3 9337 1455
6 +61 3 9337 1455
>* +61 401-716-069
>* jchenowe@bigpond.net.au
VK3AEK
-----Original Message-----
From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf
Of John Chenoweth
Sent: Tuesday, 30 October 2007 6:32 PM
To: gdb@sourceware.org
Subject: RE: Solaris Core file analysis
Hi,
I am trying to analyse a multithreaded program core dump on
solaris.
When I use the gdb command:
Thread apply all bt full
I only get some of the backtraces for each thread.
If I use the gdb command:
Maint info sol-threads
I get details of all of the user threads.
How do I get backtraces for each of the user threads?
I am using gdb 6.6.
The application is written in C++. If I use pstack, I can see
backtraces however the names are all mangled. I would also like to see
variable values.
Regards,
John Chenoweth
prev parent reply other threads:[~2007-11-02 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 7:32 John Chenoweth
2007-11-02 7:41 ` John Chenoweth [this message]
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='001a01c81d23$b82ac250$9400a8c0@zaphod' \
--to=jchenowe@bigpond.net.au \
--cc=gdb@sourceware.org \
/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