Message-Id: <3.0.6.32.19990214105438.008d1850@pop.netaddress.com> X-Sender: pderbysh AT pop DOT netaddress DOT com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 14 Feb 1999 10:54:38 -0500 To: djgpp AT delorie DOT com From: Paul Derbyshire Subject: Re: Program Exit Code 255 In-Reply-To: <36C5CF37.204E8855@epix.net> References: <36C4EA76 DOT 2AF8D76A AT epix DOT net> <36C4B354 DOT 2C8939EE AT xyz DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Reply-To: djgpp AT delorie DOT com At 11:15 AM 2/13/99 -0800, you wrote: >Then is there a way I can tell what the default error exit code 255 is? Or >is there someplace where I can find a list of errors? From a DJGPP app, errorlevel 255 usually signals a crash, such as a segfault. There's no standard on errorlevels other than that 0 means a normal successful exit and non-zero reports some kind of error. Beyond that it's up to individual apps to document the non-zero error codes they return and what these mean. DJGPP's load stub and default signal handlers will produce some error codes: 102 -- Stub couldn't find an executable image 103 -- Tried to run as a .COM file 104 -- Executable image is bad/wrong format/corrupt 105 -- Ran out of DOS (640K) mem on startup. (Stub needs this, protected mode program itself does not.) 106 -- Couldn't get to protected mode. (286???) 107 -- No DPMI selectors available. 108 -- No DPMI memory available. 109 -- DOS version 1 or 2. DJGPP apps need version 3 or later. 110 -- No DPMI at all. (No Windows/QEMM, no CWSDPMI to fall back on.) 255 -- Caught a fatal signal, such as SIGSEGV. -- .*. "Clouds are not spheres, mountains are not cones, coastlines are not -() < circles, and bark is not smooth, nor does lightning travel in a `*' straight line." ------------------------------------------------- -- B. Mandelbrot |http://surf.to/pgd.net _____________________ ____|________ Paul Derbyshire pderbysh AT usa DOT net Programmer & Humanist|ICQ: 10423848|