From: Lars Erdmann <lars DOT erdmann AT arcor DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Hooking protected mode interrupts
Date: Wed, 29 May 2002 17:09:55 +0200
Organization: Arcor
Lines: 13
Message-ID: <3CF4EF43.BC5325C9@arcor.de>
NNTP-Posting-Host: dialin-145-254-255-214.arcor-ip.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: newsread1.arcor-online.net 29643 NG bGFycy5lcmRtYW5u
X-Complaints-To: abuse AT arcor-online DOT net
NNTP-Posting-Date: Tue, 28 May 2002 15:13:18 +0000 (UTC)
X-Priority: 1 (Highest)
X-Mailer: Mozilla 4.61 [de] (OS/2; U)
X-Accept-Language: de
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hi,

I have successfully hooked a protected mode interrupt.
Now I have read in some note, that the protected mode wrapper that is
obtained via _go32_dpmi_alloc_iret_wrapper (or so) or via
_go32_chain_protected_mode_interrupt_vector (or so) is not locked by
djgpp.
Since it is essential to lock all code and data accessed during
interrupt time, I wonder if I risk a trap in my app.
Has this been fixed/changed in the newest release, maybe ?
If not, what is the workaround ?

Lars