Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!stanford.edu!agate!ucbvax!SCT60A.SUNYCT.EDU!sweetmr
From: sweetmr@SCT60A.SUNYCT.EDU (michael sweet)
Newsgroups: comp.sys.sgi
Subject: Re: Shared Memory Problems
Message-ID: <9106050138.AA05941@sct60a.sunyct.edu>
Date: 5 Jun 91 01:38:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 25

>
>In article <9106041435.AA00794@sct60a.sunyct.edu>, sweetmr@SCT60A.SUNYCT.EDU (michael sweet) writes:
|> 
|> We are developing an application which uses large amounts of shared memory
|> (about 2 Mb in the current configuration) to track different types of datafiles.
|> During integration with other pieces of the project on another machine, we
|> have run into an error/bug that gives the error:
|> 
|>  "Could not find window slot in shared memory"
|> 

Mark says:
>
>Something in your shared memory code is trashing the memory segment
>shared between the GL portion of your program and the NeWS server.

Well, most of the programs using our system *don't* use the GL library.
They generate the datafiles which are later displayed using GL calls.
Therefore, that cannot be the cause...  Perhaps I should clarify; the
person doing the testing was opening a wsh window (via her 'tools'
toolchest) and the error message appeared in the console window.

Any other ideas?

 -Mike