Mail Archives: djgpp/2001/06/30/06:00:23
On Fri, 29 Jun 2001 12:05:37 +0300, "Eli Zaretskii"
<eliz AT is DOT elta DOT co DOT il> 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.
Library code, not my own code. I assume the library code that messes
with interrupt handlers is near bulletproof after this many years, and
can safely be ignored.
>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.
Seems like a serious oversight in the implementation to me.
>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).
Show me how to get RHGDB not to die on loading the image, and maybe
I'll investigate that avenue...
--
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 -