Path: utzoo!attcan!uunet!seismo!sundc!pitstop!male!sun-arpa!ames!pasteur!ucbvax!decwrl!purdue!ha
From: ha@cs.purdue.EDU (Hiralal Agrawal)
Newsgroups: comp.windows.x
Subject: Orphan Windows under Twm
Message-ID: <6591@medusa.cs.purdue.edu>
Date: 20 Apr 89 04:08:14 GMT
Sender: news@cs.purdue.EDU
Reply-To: ha@serc3.cs.purdue.edu ()
Organization: Department of Computer Science, Purdue University
Lines: 21


Environment: Sun 3/50, X11R3, Sun Unix 4.2 Revision 3.4, Twm Revision 1.2

Sometimes when an application creates a window, maps it, and during
subsequent computation, exits due to a segmentation fault (core dump), 
the window created by the application does not go away. Worse yet, I
am unable to kill that left-over window (by xkill or twm's f.destroy). 
Also, after I fix the segmentation fault bug in the application, and 
rerun it, the left-over window some how interferes and prevents the
new window from being mapped! The only way out I know is to kill twm
and restart it. That removes the left-over window and things resume
working normally (until another core-dump, that is :-).

Has anyone else seen this behavior? Is there something that I should 
be aware of to avoid this problem? Any help will be appreciated.

-- Hiralal Agrawal
-- 
ha@cs.purdue.edu                       ARPA
ha%purdue.edu@relay.cs.net             CSNET
{ucbvax,decvax,ihnp4}!purdue!ha        UUCP