Mail Archives: djgpp/2001/06/29/01:30:05
> >Yes; and CWSDPMI did just that: you've got the EIP where your program
> >crashed. That's a lot.
>
> Unfortunately, I can't *use* it, because symify doesn't translate it
> into something that can be connected with an actual suspect line of
> code, function, variable, or anything.
You only see a message from CWSDPMI if you've trashed the protected mode
environment so severely that CWSDPMI sees impending doom due to nested
exceptions. In this case the traceback handler from DJGPP can't execute.
If you could symify the EIP, there's a real good chance it's inside the
DJGPP exception handler, or that handler was overwritten by data.
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.
> >It turns out that in your case, it _is_ too much to ask.
>
> Why?
> (Wondering if PM is all it's cracked up to be.)
The "pretty" exception handler which does tracebacks, etc is in the DJGPP
code. Bugs in your code can overwrite that code in rare instances or set
the operating stack to be invalid (oops). If you got the CWSDPMI registers,
you would have hard wedged many environments. When CWSDPMI captures the
error, it's a last chance bail to give you an idea what happened and pray
you don't have to reboot.
- Raw text -