From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4618 invoked by alias); 27 Jun 2003 01:02:52 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 4608 invoked from network); 27 Jun 2003 01:02:52 -0000 Received: from unknown (HELO mail.cps.cmich.edu) (141.209.168.43) by sources.redhat.com with SMTP; 27 Jun 2003 01:02:52 -0000 Received: from cps201.cps.cmich.edu (cps201.cps.cmich.edu [141.209.168.201]) by mail.cps.cmich.edu (Postfix) with ESMTP id 7741EC2E29; Thu, 26 Jun 2003 21:02:51 -0400 (EDT) Date: Fri, 27 Jun 2003 01:33:00 -0000 From: Eric McDonald To: Tom Lowshang Cc: xconq7 Subject: Re: (linux) xconq errors at exit In-Reply-To: <20030626225522.GA24113@low-shang.homelinux.com> Message-ID: References: <20030625212834.GA23080@low-shang.homelinux.com> <20030626014319.GB23080@low-shang.homelinux.com> <20030626160021.GA18392@low-shang.homelinux.com> <20030626225522.GA24113@low-shang.homelinux.com> X-Errors-To: emcdonal@cps.cmich.edu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003/txt/msg00254.txt.bz2 On Thu, 26 Jun 2003, Tom Lowshang wrote: > If I start xconq on console, I get "X error on display :0.0: > BadWindow (invalid Window parameter)" when xconq exits only. The > message repeat several time. This happens whether I use -g or > setup dialogs. Which Tk is this with? (Not that it probably matters; I am simply looking for data points...) Also, when you say "when xconq exits only", do you mean you watch these messages only appear on your console while Xconq is exiting and not before? And, if so, were any other Xconq windows, besides the one that contains the map displays, open? > Fatal error encountered. Signal 11 That's a segmentation fault. There is deeply entwined interaction between the Tcl/Tk part of the interface and the C part of the interface, and if something goes away in one (and its memory gets deallocated) then the other might very well get a little bit upset. Probably more safeguards could be put in place.... It's something I might investigate once I find a way to appropriately deal with the BadWindow/BadDrawable stuff. Thanks for the data, Eric