Mail Archives: djgpp/2001/06/23/18:45:10.1
On Thu, 21 Jun 2001 13:13:44 +0300 (IDT), Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> sat on a tribble, which squeaked:
>As I said earlier, I'd first suspect some stack smashage, like a huge
>automatic variable or extremely deep recursion.
Well there's no huge automatic variables. There is recursion, but I
don't think it ever goes "extremely deep". Define "extremely deep"
more precisely and I can have another look.
>You misunderstand what happens: the exception (GPF) indeed happens inside
>CWSDPMI, but the reason is outside CWSDPMI. So CWSDPMI bugs are not
>relevant here; _your_ bugs are.
Actually, both are. If CWSDPMI did a better job of not crashing, I'd
have gotten e.g. a nice stack fault with traceback to aid in
debugging.
I've also had apps crash, and then the djgpp_exception_foo stuff
proceeds to crash, causing me to get a traceback in djgpp code instead
of my own code. If there's one thing that really seriously needs
improving in djgpp, it's making crashes more consistently a) produce
useable tracebacks in the machine (i.e. the default exception handlers
and CWSDPMI need to be bulletproof, or at least closer to that ideal
than they are) and b) not cause spontaneous reboots or other screwball
phenomena that make things *really* difficult. (Sure, this seems to be
a Windoze thing, but I can hardly do all my hacking in pure DOS -- no
internet, no multitasking... Don't say the L-word, I have a Winmodem,
fortunately due to be replaced July 1.)
--
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 -