From: muppet <scott@asofyet.org>
To: "Brian Hanley" <brian.hanley@flextrade.com>
Cc: "GTK Dev List" <gtk-devel-list@gnome.org>,
"GCC Mailing List" <gcc@gcc.gnu.org>,
"GDB Mailing List" <gdb@sources.redhat.com>
Subject: Re: glib/backtrace question
Date: Wed, 09 Feb 2005 02:33:00 -0000 [thread overview]
Message-ID: <57e33384cbc9aad7d953e8de8cd0bf05@asofyet.org> (raw)
In-Reply-To: <007b01c50e46$876dd970$7408fc81@flexwin.intranet.flextrade.com>
On Feb 8, 2005, at 8:27 PM, Brian Hanley wrote:
> Whatever happened to the backtrace() and backtrace_symbols() calls in
> glib?
You're thinking of glibc, not GLib.
#include <execinfo.h>
backtrace
backtrace_symbols
backtrace_symbols_fd
These give you module & offset; you still need to use the addr2line
utility to get filename & line number information from debugging
symbols.
--
She's obviously your child. She looks like you, she talks a lot, and
most of it is gibberish.
-- Elysse, to me, of Zella.
prev parent reply other threads:[~2005-02-09 1:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 1:47 Brian Hanley
2005-02-09 2:33 ` muppet [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=57e33384cbc9aad7d953e8de8cd0bf05@asofyet.org \
--to=scott@asofyet.org \
--cc=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