Mail Archives: djgpp/2001/06/29/01:45:11.1
On Fri, 29 Jun 2001 00:08:23, "Charles Sandmann"
<sandmann AT clio DOT rice DOT edu> sat on a tribble, which squeaked:
>When this happens, I recommend setting the stack space with stubedit
>huge (like 1/2 your memory) and try again. Still crash?
>Probably in some interrupt handler or something.
I don't mess with interrupt handlers. The program does use Allegro and
activate a graphics mode with it, but it doesn't mess with the other
features of Allegro. Also, the Allegro calls are definitely not
failing any preconditions. (Plus I've occasionally had them do so, and
nothing but a stock SIGSEGV has ever resulted from mis-handling
Allegro graphics code that I've seen.) As for stack space, isn't there
a stack fault signal and presumably something to trigger it as
appropriate?
>The "pretty" exception handler which does tracebacks, etc is in the DJGPP
>code.
Maybe it should be moved. Or maybe, at least, symify can be modified
to be able to handle oddball CWSDPMI deaths. Or something. A few raw
hex numbers are thin gruel for the debugger indeed these days.
--
Bill Gates: "No computer will ever need more than 640K of RAM." -- 1980
"There's nobody getting rich writing software that I know of." -- 1980
"This antitrust thing will blow over." -- 1998
Combine neo, an underscore, and one thousand sixty-one to make my hotmail addy.
- Raw text -