Date:	Sat, 20 Dec 1997 10:34:05 -0800 (PST)
Message-Id:	<199712201834.KAA17052@adit.ap.net>
Mime-Version:	1.0
To:	jaster32 AT hotmail DOT com (Jaster), djgpp AT delorie DOT com
From:	Nate Eldredge <eldredge AT ap DOT net>
Subject:	Re: 255 error

At 04:32  12/20/1997 GMT, Jaster wrote:
>My friend can compile his program ok in DJGPP but when he trys to run
>it says....
>
>Program exit code: 255 (0x00ff)
>then in the message window it says:
>Call frame traceback:
>in function draw_sprite+25
>in function _ctrl_startup+138
>
>This doesn't happen for me when I compile it and run it... anyone know
>what he's doing wrong?? I'm stumped.. I can send source code if you
>need to look at it...
I think the question is what *you're* doing wrong. :) Your error message is
rather abbreviated but errors giving tracebacks are almost invariably caused
by program bugs. If it mentions signal SIGSEGV, you have an invalid memory
access; probably a NULL, uninitialized or overrun pointer. SIGFPE refers to
a math error of some kind; check for divisions by zero, sqrt(negative), etc.
Is your friend using DOS and you use Windows? That could be the reason for
the difference: CWSDPMI server used under DOS can catch NULL pointer
dereferences, but Windows can't. 

Nate Eldredge
eldredge AT ap DOT net

- Raw text -