From: jaster32 AT hotmail DOT com (Jaster) Newsgroups: comp.os.msdos.djgpp Subject: Re: 255 error Date: Sun, 21 Dec 1997 06:25:42 GMT Organization: NssM Software Lines: 36 Message-ID: <349cb607.43036066@news.earthlink.net> References: <199712201834 DOT KAA17052 AT adit DOT ap DOT net> NNTP-Posting-Host: 207.217.143.249 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk On Sat, 20 Dec 1997 18:34:05 GMT, Nate Eldredge 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 =)