Mail Archives: djgpp/2002/05/29/03:58:38
Hi,
I understand, that I have to lock my OWN code and data.
However, the wrapper function that I allocate via the below mentioned
functions are NOT MY code.
So my question was if those wrapper functions are locked by the API
calls themselves.
It's a problem for me to do that since (at least for
_go32_chain_protected_mode_interrupt_vector) I do not get the address of
the wrapper function returned and besides, I don't know its length.
But the other post from Eli Zaretskji clarified that the wrapper
function is locked by the APIs themselves, so there is nothing to worry.
Thanks for your help,
Lars
Martin Str|mberg schrieb:
>
> 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 -