This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Call Stack Trace
- From: Ian Lance Taylor <iant at google dot com>
- To: Brian McGrew <brian at visionpro dot com>
- Cc: <gcc-help at gcc dot gnu dot org>
- Date: Tue, 29 Sep 2009 23:57:31 -0700
- Subject: Re: Call Stack Trace
- References: <C6E80360.14BAB%brian@visionpro.com>
Brian McGrew <brian@visionpro.com> writes:
> I need to take a look at a call stack, but without using gdb. Is there a
> macro or something similar to __FILE__ or __LINE__ that will tell me who
> called the function that I'm in???
>
> So if I have a function called foo() that gets called 100 different ways
> from differnet shared libraries and executables, how can I find out who
> called foo(), without gdb and without touching all my source code and
> putting printf's???
What processor? It matters.
I don't quite understand the bit about "without touching all my source
code". If you don't want to touch your source code, and you don't
want to use gdb, what do you want to use?
If you can change the source code a bit, see __builtin_return_address
in the docs; consider using it with the addr2line program. See also
the -finstrument-functions option.
Ian