From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16281 invoked by alias); 15 Jan 2004 21:26:17 -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 16232 invoked from network); 15 Jan 2004 21:26:15 -0000 Received: from unknown (HELO mail.broadpark.no) (217.13.4.2) by sources.redhat.com with SMTP; 15 Jan 2004 21:26:15 -0000 Received: from famine (217-13-20-38.dd.nextgentel.com [217.13.20.38]) by mail.broadpark.no (Postfix) with ESMTP id B9D3278A1D for ; Thu, 15 Jan 2004 22:26:14 +0100 (MET) Subject: Crash in xserv 4.3.0-40 From: =?ISO-8859-1?Q?=D8yvind?= Harboe To: cygwin-xfree@cygwin.com Content-Type: text/plain; charset=UTF-8 Organization: Zylin AS Message-Id: <1074201974.25360.81.camel@famine> Mime-Version: 1.0 Date: Thu, 15 Jan 2004 21:26:00 -0000 Content-Transfer-Encoding: 8bit X-SW-Source: 2004-01/txt/msg00383.txt.bz2 List-Id: Hi Harold, I'll be sure to follow up on your latest testing tips. Q: is there any reason not to include symbol information in your testing builds? Read on.... However, here are the latest and greatest: - I'm pretty sure that the crash isn't there when I compiled and installed the sources as I described. - I've recently discovered core dumps! Here is a post that describes it a bit: http://www.cygwin.com/ml/cygwin-patches/2000-q3/msg00041.html So, armed with core dumps, my strategy is as follows: - uninstall everything and reinstall cygwin from scratch w/latest xserv. - add the following line to the beginning of startxwin.bat set cygwin=error_start=c:\cygwin\bin\dumper.exe - wait for the crash - Recompile w/debug info - Wait for crash - Coredump anyone? :-) Øyvind