This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
RE: Solaris Core file analysis
- From: "John Chenoweth" <jchenowe at bigpond dot net dot au>
- To: <gdb at sourceware dot org>
- Date: Fri, 2 Nov 2007 18:40:57 +1100
- Subject: RE: Solaris Core file analysis
- Reply-to: <jchenowe at bigpond dot net dot au>
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