Mail Archives: djgpp/1995/07/10/09:03:12
> It seems to me that the stack created for you when you call
> _go32_allocate_iret_wrapper is never locked. If this is so either
> there is something I don't know about or that is a bug. Also,
Bug.
> shouldn't the variable that points to the malloc()'ed stack (the one
> that get's loaded into %esp) be locked as well? And shouldn't the
> entire wrapper code be locked as well? Just curious, because we know
> that this code and data will be accessed from within an interrupt...
Probably. V1 never got locking right. Feel free to fix it, but I
don't plan on any more V1 releases since V2 is so close to release.
How about getting V2 and fixing it there? V2 might have the same type
of problem.
- Raw text -