Date: Thu, 11 Apr 1996 10:17:15 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Shawn Lee <sdlee AT atlanta DOT com>
Cc: The DJGPP Mailing List <djgpp AT delorie DOT com>
Subject: Re: Running the test program
In-Reply-To: <316A3C9C.7EBA@atlanta.com>
Message-Id: <Pine.SUN.3.91.960411101034.27524D@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 9 Apr 1996, Shawn Lee wrote:

> Has anyone ever experienced a problem with running any codes on a Win95-
> Pentium w/16MByte.  When I run the test programs, it is a toss-up if
> they work or not.  I DO MEAN TOSS-UP.

Did you try to debug your program?  Nobody ever said that bugs must 
behave the same way every time you invoke the program; referencing an 
uninitialized memory location might result in what you see.

Does that SIGSEGV come with a stack trace dump?  If so, there is a program
named `symify' that comes with DJGPP that should help you to translate
that dump into a human-readable list of source filenames and line numbers
that led to the crash.  The DJGPP FAQ list (v2/faq200b.zip from ther same
place you get DJGPP) explains how to do it in section 9.2.  Armed with
that knowledge, you can see if there is any bug in your program. 

If you are sure that your program is not the reason, please at least post 
the source (if it's short enough) or its fragment that crashes.  The 
exact message printed when the program dies will also help a lot.