Xref: news-dnh.mv.net comp.os.msdos.djgpp:816
Path: news-dnh.mv.net!mv!news.sprintlink.net!howland.reston.ans.net!vixen.cso.uiuc.edu!news.uoregon.edu!premier3.premier.net!uunet!in1.uu.net!nwfocus.wa.com!news.telebyte.com!usenet
From: jhunter AT kendaco DOT telebyte DOT com (Joel Hunter)
Newsgroups: comp.os.msdos.djgpp
Subject: V. 2.0 _go32_allocate_iret_wrapper stack not locked?
Date: Sat, 08 Jul 1995 05:21:24 GMT
Organization: Telebyte North West Silverdale, Wa
Lines: 10
Nntp-Posting-Host: kendaco.telebyte.com
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

  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,
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...