From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-20656-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 8074 invoked by alias); 9 Feb 2005 01:34:33 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 8051 invoked from network); 9 Feb 2005 01:34:26 -0000
Received: from unknown (HELO mailproxy.dmz.flextrade.com) (167.206.176.233)
  by sourceware.org with SMTP; 9 Feb 2005 01:34:26 -0000
Received: from blazer.unix.intranet.flextrade.com (blazer.unix.intranet.flextrade.com [129.252.8.42])
	by mailproxy.dmz.flextrade.com (8.12.10/8.12.10) with ESMTP id j191YMFZ013961;
	Tue, 8 Feb 2005 20:34:23 -0500
Received: from golf (golf.flexwin.intranet.flextrade.com [129.252.8.116])
	by blazer.unix.intranet.flextrade.com (8.12.5/8.12.5) with ESMTP id j191YMkY025533;
	Tue, 8 Feb 2005 20:34:22 -0500
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
Message-ID: <007b01c50e46$876dd970$7408fc81@flexwin.intranet.flextrade.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Synonym: Message copied to feb05@mailproxy by Synonym (http://www.modulo.ro/synonym)
X-SW-Source: 2005-02/txt/msg00051.txt.bz2

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
_________________________________________