home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!enterpoop.mit.edu!eru.mt.luth.se!lunic!sunic!seunet!pop!bjst
- From: bjst@sth.frontec.se (Bjorn Stenberg)
- Newsgroups: comp.sys.amiga.programmer
- Subject: WShell: Hangning forbid!
- Message-ID: <1992Dec12.143541.21468@sth.frontec.se>
- Date: 12 Dec 92 14:35:41 GMT
- Organization: IDK/Frontec - System Design Group
- Lines: 26
- Nntp-Posting-Host: pop.sth.frontec.se
-
-
- A while ago there was some talk about process syncronization when
- multithreading, and Randell Jesup suggested doing:
-
- ...
- Forbid();
- Signal(parent,sig); // tell parent we exited
- }
-
- to make sure the child has exited before any other process gets a time slice.
-
- Well, I do this in a child of mine, but after the parent exits WShell
- complains with the message:
-
- ***Hanging forbid!
-
- Is WShell just being paranoid or am I doing something wrong? (I'm not supposed
- to Permit() or anything in the parent, am I?)
-
- Any hints are appreciated.
-
- -- Bjorn
-
- ---------------------------------------------------------------------------
- Bjorn Stenberg, Stockholm, Sweden bjst@sth.frontec.se
- ---------------------------------------------------------------------------
-