From:	Martin Str|mberg <ams AT speedy DOT ludd DOT luth DOT se>
Subject:	Re: Hooking protected mode interrupts
Newsgroups:	comp.os.msdos.djgpp
References:	<3CF4EF43 DOT BC5325C9 AT arcor DOT de>
User-Agent:	tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (NetBSD/1.5_BETA (alpha))
Message-ID:	<1022611296.485030@queeg.ludd.luth.se>
Cache-Post-Path:	queeg.ludd.luth.se!unknown AT speedy DOT ludd DOT luth DOT se
X-Cache:	nntpcache 2.4.0b5 (see http://www.nntpcache.org/)
Date:	28 May 2002 18:41:36 GMT
Lines:	23
NNTP-Posting-Date:	28 May 2002 18:41:36 GMT
NNTP-Posting-Host:	queeg.ludd.luth.se
X-Trace:	1022611296 news.luth.se 283 130.240.16.109
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Lars Erdmann <lars DOT erdmann AT arcor DOT de> wrote:
: 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.

Yes.

: Has this been fixed/changed in the newest release, maybe ?

There's nothing to fix.

: If not, what is the workaround ?

To lock it (ummm, I must misunderstand you because this is obvious)!


Right,

						MartinS

- Raw text -