Re: Recursion crash in STL on linux
On Apr 28, 10:56 am, =D6=F6 Tiib <oot...@hot.ee> wrote:
On Apr 28, 12:17 pm, boltar2...@boltar.world wrote:
On Wed, 28 Apr 2010 02:31:06 +0200
Sjouke Burry <burrynulnulf...@ppllaanneett.nnll> wrote:
Are you sure that the problem is the stack limit and not
another form of memory corruption? What does the debugger
tell you?
Last time I had a stack problem, I just wrote a very small
assembler routine, to return the value of the stackpointer.
That value, as the stack became full , moved to zero. So
if your system works likewise, use such a routine to quit
at the right moment, while there is still some left.
Is there a way of doing that in C rather than assembler? My
x86 assembler isn't great but I want the program to be
portable anyway.
There are no way to do it in C because stack and its location,
size and direction are platform specific. There may be
platform specific libraries that have functions to do
something in C. If there are none then you may have to write
it (or parts of it) in assember.
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++.)
If you have implementation that should be portable and that
depends on properties of stack then you end up having that
functionality differently implemented for each plaform used.
So you should perhaps enwrap it behind common interface to
keep your code readable.
Yes. This is the usual solution.
--
James Kanze