From: "Maucci, Cyrille" <cyrille.maucci@hp.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
"Maucci, Cyrille" <cyrille.maucci@hp.com>
Subject: RE: Backtrace extraction ONLY gdb
Date: Wed, 23 Mar 2011 22:17:00 -0000 [thread overview]
Message-ID: <0E02F16954AF394BB163AEE50FDF548569009DAB5A@GVW1121EXC.americas.hpqcorp.net> (raw)
In-Reply-To: <8339mg9unq.fsf@gnu.org>
Hi Eli, All,
Yes that is a glibc based system.
I imagine you are referring to http://www.gnu.org/s/libc/manual/html_node/Backtraces.html
From what I read it gives a very 'raw' output, very far from the beautiful gdb backtrace with function names and function arguments values.
But that is a beginning.
Thanks a lot
++Cyrille
-----Original Message-----
From: Eli Zaretskii [mailto:eliz@gnu.org]
Sent: Monday, March 21, 2011 7:49 PM
To: Maucci, Cyrille
Cc: gdb@sourceware.org
Subject: Re: Backtrace extraction ONLY gdb
> From: "Maucci, Cyrille" <cyrille.maucci@hp.com>
> CC: "Maucci, Cyrille" <cyrille.maucci@hp.com>
> Date: Mon, 21 Mar 2011 17:13:02 +0000
>
> So, that is the kind of barrier I need to work around because for support reasons, I dramatically need a single feature of gdb on such systems which is the backtrace extraction feature.
>
> Is there any possibility to 'recompile' gdb where only the 'bt' (or 'threads apply all bt') feature would be enabled?
If that system is GNU/Linux (or anything else glibc-based), then you should know that there's a glibc function that can produce a backtrace.
next prev parent reply other threads:[~2011-03-23 22:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 17:13 Maucci, Cyrille
2011-03-21 18:49 ` Eli Zaretskii
2011-03-23 22:17 ` Maucci, Cyrille [this message]
2011-03-23 22:43 ` Joel Brobecker
2011-03-23 22:51 ` Maucci, Cyrille
2011-03-24 5:25 ` Jan Kratochvil
2011-03-27 20:26 ` Maucci, Cyrille
2011-04-22 20:49 ` Maucci, Cyrille
2011-04-22 20:54 ` Jan Kratochvil
2011-03-24 10:25 ` Pedro Alves
2011-03-24 11:09 ` Maucci, Cyrille
2011-03-24 10:28 ` Steffen Dettmer
2011-03-24 13:01 ` Jan Kratochvil
2011-03-22 16:46 ` Tom Tromey
2011-03-23 22:21 ` Maucci, Cyrille
2011-03-24 17:13 ` Tom Tromey
2011-03-24 17:20 ` Jan Kratochvil
2011-03-24 19:00 ` Maucci, Cyrille
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=0E02F16954AF394BB163AEE50FDF548569009DAB5A@GVW1121EXC.americas.hpqcorp.net \
--to=cyrille.maucci@hp.com \
--cc=eliz@gnu.org \
--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