Re: print stack...

From:

James Kanze <james.kanze@gmail.com>

Newsgroups:

comp.lang.c++

Date:

Wed, 17 Oct 2007 00:17:06 -0700

Message-ID:

<1192605426.065541.206070@v29g2000prd.googlegroups.com>

On Oct 17, 8:56 am, red floyd <no.s...@here.dude> wrote:

James Kanze wrote:

On Oct 16, 8:20 pm, red floyd <no.s...@here.dude> wrote:

call_me_anything wrote:

[...]

Is there something similar, which can print the current stack ?
I mean some C/C++ API which can help me get any info related to the
current stack of functions.
Thats is required for debugging.
(Please do not suggest gdb... I want something similar to gdb stack
traces but that should print stack info everytime I compile with DEBUG
on)

[redacted]
Your implementation has two major problems: it requires that
every function use the TRACE macro, it skips functions which
don't use the macro; and it fails radically in a multi-thread
environment.

1. You're right, it does require the TRACE macro and skips
those that don't.

2. You're right. I wrote the original version years ago in a
single threaded environment. However, if I *really* wanted to
be pedantic, I'd note that multithreaded environments are OT
in comp.lang.c++... :-).

Neither of which, of course, means that it isn't useful. As
long as you know and understand its limitations. It's a lot,
lot simpler than the stack walkback that I use, which requires a
new implementation for every platform.

--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34