Date:	Sun, 4 Jul 1999 16:35:46 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Wei Luo <luo AT geog DOT niu DOT edu>
cc:	djgpp AT delorie DOT com
Subject:	Re: SIGABRT
In-Reply-To:	<Pine.SOL.3.96.990701211351.29579A-100000@taiga>
Message-ID:	<Pine.SUN.3.91.990704163351.13333f-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 1 Jul 1999, Wei Luo wrote:

> I have a program that works fine when I compile and run 
> on a Sun Solaris system. When I try to compile it on my PC
> (running Windows NT) with djgpp, it went fine. But when I try
> to run it, I got the following message 
> 	"Program has received signal: SIGABRT, Aborted"
> With rhide debugging tool, I can pin point that it bombs out
> right after statement
> 	    if ((fpt = fopen(filename,"wb")) == NULL)
>                 printf("save file could not be opened\n");
> or sometimes after statement
>             (void) fwrite(c,sizeof(c),1,fpt);

Is this program compiled with DJGPP v2.02?  If not, I suggest
rebuilding it with v2.02; then, when the program crashes, you should
see a traceback that will tell where *exactly* did the program crash.
If you are getting this inside RHIDE, issue the backtrace command,
it will show you the sequence of function calls that led to the crash.
This should provide either a clue to what goes wrong, or a place to
begin debugging.

If you already get a traceback, please post it in its entirety here,
after running SYMIFY on it.  If you are getting this inside RHIDE,
post here the last portion of what backtrace displays.

For more related information, see sections 9.2 and 12.2 of the FAQ.

- Raw text -