X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Strange runtime error
Date:	Mon, 09 Feb 2004 19:25:59 CST
Organization:	Rice University, Houston, TX
Lines:	27
Message-ID:	<40283327.sandmann@clio.rice.edu>
References:	<be40988 DOT 0402091609 DOT 2ae1269e AT posting DOT google DOT com>
NNTP-Posting-Host:	clio.rice.edu
X-Trace:	joe.rice.edu 1076377892 19732 128.42.105.3 (10 Feb 2004 01:51:32 GMT)
X-Complaints-To:	abuse AT rice DOT edu
NNTP-Posting-Date:	Tue, 10 Feb 2004 01:51:32 +0000 (UTC)
X-NewsEditor:	ED-1.5.9
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> Stack Fault at eip=0000163d

You have messed up the stack.

> ebp=0011f4b0 esp=ffedf460 

ESP (the stack pointer) is unreasonable.

> App stack: [0011f4d4..0009f4d4]  

both ESP and EBP should be between these two values.

> Is that 512MB or 512KB?  

512KB is the stack default - the difference between the two hex values above
confirms that's how much you have been allocated.  

Use of larage arrays at a routine scope, or highly recursive routines
can exceed this amount.  If needed you can increase this amount using stubedit
or specifying the stklen (?) variable.

It's hard to know for sure how ESP was smashed, but it appears that ESP
is around 0x240000 below EBP, so look for arrays around that size (2.25 MB).

> It's quite possible I have used more than 512KB of static variables in my 

Static variables don't count against this limit.  

- Raw text -