Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Brian Hanley" <brian.hanley@flextrade.com>
To: "GTK Dev List" <gtk-devel-list@gnome.org>,
	"GDB Mailing List" <gdb@sources.redhat.com>,
	"GCC Mailing List" <gcc@gcc.gnu.org>
Subject: glib/backtrace question
Date: Wed, 09 Feb 2005 01:47:00 -0000	[thread overview]
Message-ID: <007b01c50e46$876dd970$7408fc81@flexwin.intranet.flextrade.com> (raw)

Hi All,

Whatever happened to the backtrace() and backtrace_symbols() calls in
glib?
I came across a magazine article from a few years back where the author
was
using the "backtrace()" and "backtrace_symbols()" calls in order to
print
a backtrace during program execution.

I can't find those calls in glib anymore.

It seems that the preferred way of doing this now is to take a gcore,
and
start up a new gdb process to examine the stack, or to use a perl script
to translate the symbol names.

I would prefer to print a dynamic backtrace from within the process
being traced.

Are there currently glib function calls which allow me to walk the
stack?
Is there an interface in the gdb code that I can link to for a dynamic
backtrace?
Is there another library or other code which allows for dynamic
backtraces?

Brian

_________________________________________
 Brian Hanley, Software Developer
 FlexTrade Systems - Great Neck, NY 11021
 brian.hanley@flextrade.com
 +1 (516) 627-8993 Ext. 238
_________________________________________


             reply	other threads:[~2005-02-09  1:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09  1:47 Brian Hanley [this message]
2005-02-09  2:33 ` muppet

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='007b01c50e46$876dd970$7408fc81@flexwin.intranet.flextrade.com' \
    --to=brian.hanley@flextrade.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=gtk-devel-list@gnome.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