This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Programmatic access to stack traces in C or C++ programs

From: Daniel Jacobowitz <drow at false dot org>
To: Ashwin Bharambe <ashwinb at gmail dot com>
Cc: gdb at sourceware dot org
Date: Fri, 20 Oct 2006 10:27:38 -0400
Subject: Re: Programmatic access to stack traces in C or C++ programs
References: <3ef5826d0610191927n590c416fx238aa355a378d57c@mail.gmail.com> <20061020031303.GA11223@nevyn.them.org> <3ef5826d0610200541g4804ec15sc2b3167b455c735e@mail.gmail.com>

On Fri, Oct 20, 2006 at 08:41:07AM -0400, Ashwin Bharambe wrote:
> Sweet. Thanks Daniel for pointing me to libunwind.. Now, given the
> instruction pointer and stack pointer values, do you think I can use
> some parts of gdb code to dump out a more readable version of the
> stackframe? It would be _really_ nice if I could dump out argument
> values as well, but I suspect that might be much harder.

GDB is really not set up to reuse this way.

-- 
Daniel Jacobowitz
CodeSourcery

References:
- Programmatic access to stack traces in C or C++ programs
  - From: Ashwin Bharambe
- Re: Programmatic access to stack traces in C or C++ programs
  - From: Daniel Jacobowitz
- Re: Programmatic access to stack traces in C or C++ programs
  - From: Ashwin Bharambe

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]