Mail Archives: djgpp/2000/03/15/20:57:16
On Tue, 14 Mar 2000 11:51:30 +0100, Michael Tippach <mtippach AT gmx DOT net>
wrote:
>Not as dangerous as SS ("Stack Suicide") in these environments. It would
>always fault at the IRET when the DPMI host finally returns from the
>interrupt handling code. If the IRET would have been a ring transition,
>this would be no good, I suppose. For, a DPMI host running its client at
>ring 3 would not really be prepared to convert exceptions occuring in
>ring 0 into DPMI compliant ones at ring 3 (something to try out,
>really). Then again, if the IRET does NOT cause a ring transition, the
>DPMI host would have very little interest in looking at the source of
>the exception. Business as usual, in that case.
>
>I think that would be the easiest way to fix the NT signal problem,
>because it can be implemented at very little cost (few lines of code)
>without breaking any existing code I could think of.
Then how about writing up a proof-of-concept implementation
and sending the diffs to the djgpp-workers list?
--
Damian Yerrick http://yerricde.tripod.com/
Comment on story ideas: http://home1.gte.net/frodo/quickjot.html
AOL is sucks! Find out why: http://anti-aol.org/faqs/aas/
View full sig: http://www.rose-hulman.edu/~yerricde/sig.html
This is McAfee VirusScan. Add these two lines to your .sig to
prevent the spread of .sig viruses. http://www.mcafee.com/
- Raw text -