Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: "Maucci, Cyrille" <cyrille.maucci@hp.com>
Cc: Eli Zaretskii <eliz@gnu.org>, "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Backtrace extraction ONLY gdb
Date: Wed, 23 Mar 2011 22:43:00 -0000	[thread overview]
Message-ID: <20110323224339.GS2534@adacore.com> (raw)
In-Reply-To: <0E02F16954AF394BB163AEE50FDF548569009DAB5A@GVW1121EXC.americas.hpqcorp.net>

> >From what I read it gives a very 'raw' output, very far from the
> >beautiful gdb backtrace with function names and function arguments
> >values.

You would be indeed missing the function argument values.  But
getting the function names from the addresses can be done later on,
using a tool such as addr2line.

The best option, IMO, is to get your process to dump a core file.
You'd then debug on a separate host using that core file. A few
companies I know do that routinely.

-- 
Joel


  reply	other threads:[~2011-03-23 22:43 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
2011-03-23 22:43     ` Joel Brobecker [this message]
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=20110323224339.GS2534@adacore.com \
    --to=brobecker@adacore.com \
    --cc=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