From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2446 invoked by alias); 6 Jan 2004 15:48:08 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Reply-To: cygwin-xfree@cygwin.com Received: (qmail 2436 invoked from network); 6 Jan 2004 15:48:07 -0000 Received: from unknown (HELO central.ixn.com) (65.19.132.2) by sources.redhat.com with SMTP; 6 Jan 2004 15:48:07 -0000 Received: from msu.edu (office.ixn.com [68.23.74.57]) (authenticated bits=0) by central.ixn.com (8.12.10/8.12.10) with ESMTP id i06FlsMN024557 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 6 Jan 2004 10:47:56 -0500 (EST) Message-ID: <3FFAD8A2.4000505@msu.edu> Date: Tue, 06 Jan 2004 15:48:00 -0000 From: Harold L Hunt II User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: Re: XFree86-xserv-4.3.0-32 tests References: <1073401938.2637.6.camel@famine> In-Reply-To: <1073401938.2637.6.camel@famine> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=0.0 required=5.5 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) X-SW-Source: 2004-01/txt/msg00118.txt.bz2 List-Id: Øyvind, I wouldn't worry too much about it... I am in the middle of completely reworking the clipboard shutdown code. The crashes will be fixed when I am through with it, so I don't particularly need details about any current crashes in -32 anymore. Thanks for testing, Harold Øyvind Harboe wrote: > I've now seen the xwinclip: xwin.exe crash on exit with > 4.3.0-32 as well. It was an access violation to address 1. > > Is this a known problem? > > If not, does anyone have any pointers on how to create a useful bug report? > > One idea I had was to somehow invoke GDB once the OK Cancel access violation requester > pops up, but I've no idea on how to go about this? > > A fixed sequence of steps to reproduce the problem has eluded me, hence my > interest in a postmortem approach. > > > Øyvind > > > >