Mail Archives: djgpp/2001/06/29/06:45:19
> From: invalid AT erehwon DOT invalid (Graaagh the Mighty)
> Newsgroups: comp.os.msdos.djgpp
> Date: Fri, 29 Jun 2001 05:37:18 GMT
>
> 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.
Yes, you do: every DJGPP program installs a handler for the hardware
keyboard interrupt in the startup code. It also installs a handler
for Int 75h, the FPU interrupt.
> As for stack space, isn't there a stack fault signal and presumably
> something to trigger it as appropriate?
Yes, but since the stack is really just a part of the DS segment, and
SS is loaded with the same selector as DS, you can't have this signal
when the stack overflows, because the protection mechanism cannot
detect it.
> >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.
Just use the EIP CWSDPMI prints; it's a starting point for debugging.
(I explained in another message how to get the function name and the
source line given the EIP value).
- Raw text -