home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!barmar
- From: barmar@think.com (Barry Margolin)
- Newsgroups: comp.lang.lisp
- Subject: Re: Lucid 4, process help
- Date: 16 Dec 1992 20:06:53 GMT
- Organization: Thinking Machines Corporation, Cambridge MA, USA
- Lines: 21
- Distribution: comp
- Message-ID: <1go28tINNloe@early-bird.think.com>
- References: <23064@venera.isi.edu>
- NNTP-Posting-Host: telecaster.think.com
-
- In article <23064@venera.isi.edu> jas@ISI.EDU (Jeff Sullivan) writes:
- >I'm trying to set up a system where several processes are run in the
- >background, controlling CLIM applications, and are controlled in some
- >part by a forground processes, which is itself a CLIM application.
- >
- >Now, the only problem comes when trying to quit from the main process.
- >I try to issue a KILL-PROCESS to each of the sub-processes, and
- >sometimes (not all the time, but not reproducably), I get the
- >following error:
- >
- >>>Error: Attempting to unlock a lock held by #<Process Summary Window 1DE823E>
-
- It would help if you included a stack trace, but what is suspect is
- happening is that the subprocesses are all trying to close their windows
- concurrently, and there's a problem in the locking protocol that's supposed
- to prevent contention for the CLX root window.
- --
- Barry Margolin
- System Manager, Thinking Machines Corp.
-
- barmar@think.com {uunet,harvard}!think!barmar
-