Mail Archives: djgpp/1997/12/21/03:45:33
On Sat, 20 Dec 1997 18:34:05 GMT, Nate Eldredge <eldredge AT ap DOT net>
wrote:
>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
>
>
>
Thanks for the help but that wasn't the problem.. the moron sent me
the wrong source code so I was compiling source that I had already
fixed for him.. the error was because he was drawing to a bitmap
before he had created it using create_bitmap(x,y).. but thanks a lot
for you help =)
- Raw text -