Re: Recursion crash in STL on linux

From:

James Kanze <james.kanze@gmail.com>

Newsgroups:

comp.unix.programmer,comp.lang.c++

Date:

Thu, 29 Apr 2010 09:30:34 -0700 (PDT)

Message-ID:

<986337c8-8dac-420f-bc04-8ae122c0f061@r11g2000yqa.googlegroups.com>

On Apr 28, 8:20 pm, sc...@slp53.sl.home (Scott Lurndal) wrote:

James Kanze <james.ka...@gmail.com> writes:

On Apr 28, 10:56 am, =D6=F6 Tiib <oot...@hot.ee> wrote:

On Apr 28, 12:17 pm, boltar2...@boltar.world wrote:

[...]

It's normally no problem to get the address of the stack in C or
C++; just take the address of a local variable. (This isn't
guaranteed by the standard, of course, which doesn't even
guarantee that there is a stack, per se.) What that address
means, and what information you can deduce from it, is very
implementation specific, but for a given platform, you can often
determine something. (I've written stack walkback routines for
a number of platforms in C++. The code for one platform doesn't
work on other platforms, but it's still C++.)

GCC/G++/GLIBC has this built-in now:

G++ has had it for some time now, I think. But I had originally
implemented the code for VC++ and Sun CC, and I'm not sure that
g++ supported it when I originally wrote the code. Were I doing
it today, I'd certainly use the g++ function for the g++
versions of the code.

--
James Kanze