Sender: nate AT cartsys DOT com Message-ID: <36BCE1D2.DC572EDB@cartsys.com> Date: Sat, 06 Feb 1999 16:44:02 -0800 From: Nate Eldredge X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.0.36 i586) MIME-Version: 1.0 To: djgpp AT delorie DOT com Subject: Re: djgpp stack overflow References: <79fdhh$s5o$1 AT public DOT ndh DOT net> <79hujt$iio$1 AT public DOT ndh DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp AT delorie DOT com Felix Natter wrote: > > well, now i'm answering myself, i guess there's no other way (you can't > append your own messages, can you?) > Someone has asked me about this, too, and i thought I'd reply because > it may be of interest to others as well. > In the FAQ (2.01) there is a section about changing the stack size, it tells > you most of the stuff i asked in detail > (look for: search by problem description and you'll find it) > however, i still don't know how one could debug stack overflows using rhide > 1.4/stubify or whatever > if anyone has the experience, please reply! In DJGPP v2.02, the crash traceback includes the address of the stack. If the value given for esp is below that, you've (probably) overflowed the stack. Upgrade. -- Nate Eldredge nate AT cartsys DOT com