home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!spool.mu.edu!yale.edu!ira.uka.de!math.fu-berlin.de!news.netmbx.de!Germany.EU.net!mcsun!sunic!seunet!pop!bjst
- From: bjst@sth.frontec.se (Bjorn Stenberg)
- Subject: Re: WShell: Hangning forbid!
- Message-ID: <1992Dec14.092632.13758@sth.frontec.se>
- Nntp-Posting-Host: pop.sth.frontec.se
- Organization: IDK/Frontec - System Design Group
- References: <1992Dec12.143541.21468@sth.frontec.se> <1992Dec13.074137.188@jato.jpl.nasa.gov>
- Date: 14 Dec 92 09:26:32 GMT
- Lines: 19
-
- bjst@sth.frontec.se (Bjorn Stenberg) writes:
- > >Well, I do this in a child of mine, but after the parent exits WShell
- > >complains with the message:
- > >
- > >***Hanging forbid!
-
- jdickson@jato.jpl.nasa.gov (Jeff Dickson) writes:
- > My guess is that you are mistakenly letting the forbid hang in the parent
- > process.
-
- You guessed right. A silly little bug caused both processes to use the
- same clean-up code, thus the parent also Forbid()ed.
- Thanks for the tip.
-
- -- Bjorn
-
- ---------------------------------------------------------------------------
- Bjorn Stenberg, Stockholm, Sweden bjst@sth.frontec.se
- ---------------------------------------------------------------------------
-