Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!csd4.milw.wisc.edu!bbn!mit-eddie!uw-beaver!rice!sun-spots-request
From: tots!eltoro!tep%suntan.West@sun.com (Tom Perrine x426)
Newsgroups: comp.sys.sun
Subject: "window lock broken"
Keywords: Windows
Message-ID: <3629@kalliope.rice.edu>
Date: 22 May 89 18:46:44 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 26
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 12, message 7 of 15

Environment: SW: SunOS 3.5/3.5.1	HW: Sun-3/260C

We are getting occasional "window lock broken because process XXX blocked"
messages. This only happens when we are doing menu things (menu selection)
in process XXX.

I am fairly sure that we are seeing this because we are running a
home-brew pseudo-real-time scheduler on top of the regular scheduler.  (I
inherited it.)

My question is: Where is this message documented? I can't find it
anywhere. I think that it means that some process wanted to write into a
locked region but found that some other process which held a lock on that
region was in the "blocked" state, and broke the lock.

If this is the case, we may be able to hack the real-time scheduler to
notice when window things are happening.

I am an OS person, but not (yet) a window person, so any pointers would be
greatly appreciated.

Tom Perrine
Logicon				Internet:
Tactical and Training Systems	hamachi!tots!tep@NOSC.MIL
San Diego CA			UUland:
(619) 455-1330			uunet!nosc!hamachi!tots!tep