From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id: <199908191644.SAA11166@father.ludd.luth.se>
Subject: stack overruns (was: fixed stack size)
To: djgpp-workers AT delorie DOT com (DJGPP-WORKERS)
Date: Thu, 19 Aug 1999 18:44:28 +0200 (MET DST)
X-Mailer: ELM [version 2.4ME+ PL15 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

As my ideas about overcoming the fixed stack size seems to be hard or
impossible to implement, I have another idea.

What if we put a certain value at the bottom of the stack (last
position of the stack before overflowing) at the time of startup and
then check this value when exiting and if it's not what was put there
print "Possible stack overflow". Also add this check in the crash dump
handling routine and print "Almost certain stack overflow" if the
value is not right.

?


Right,

							MartinS