Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: jao@clint.uucp (John Oswalt)
Newsgroups: comp.sys.sun
Subject: Unwanted Sunview WIN ioctl messages
Keywords: Windows
Message-ID: <2749@clint.megatest.UUCP>
Date: 13 Mar 89 21:47:10 GMT
Sender: usenet@rice.edu
Organization: Megatest Corporation, San Jose, Ca
Lines: 28
Approved: Sun-Spots@rice.edu
Original-Date: 7 Mar 89 19:21:50 GMT
X-Sun-Spots-Digest: Volume 7, Issue 194, message 13 of 15

I have a Sunview application which creates a frame and some subframes,
registers several file descriptor handlers with the notifier (it processes
input from other processes through pipes), and interacts with the user a
lot.

Eventually I do a window_destroy() on the main frame, window_main_loop()
returns, and my program terminates.

Now, Sunview spits out several messages:

WIN ioctl number 20006703: Device busy
WIN ioctl number C00C671D: Bad file number
WIN ioctl number C014671F: Bad file number
WIN ioctl number C0146720: Bad file number
WIN ioctl number 2000671E: Bad file number
WIN ioctl number C00C671D: Bad file number
WIN ioctl number C014671F: Bad file number
WIN ioctl number C0146720: Bad file number
WIN ioctl number 2000671E: Bad file number
WIN ioctl number C00C671D: Bad file number
WIN ioctl number C014671F: Bad file number
WIN ioctl number C0146720: Bad file number
WIN ioctl number 2000671E: Bad file number

How can I get rid of these?
-- 

John Oswalt (..!sun!megatest!jao)