Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 30 Dec 2004 15:15:22 -0800
From:	David Hinds <dhinds AT sonic DOT net>
To:	Cygwin List <cygwin AT cygwin DOT com>
Subject:	Re: A vexing installation problem
Message-ID:	<20041230231522.GA24203@sonic.net>
Mime-Version:	1.0
User-Agent:	Mutt/1.4.2i

On Thu, 2 Dec 2004 at 09:36:21 AM -0500, Christopher Faylor wrote:

> Could you try running this under gdb to see if you get more of a clue
> about where cygwin is dying?  The last entry in the snapshot is not
> necessarily indicative of this.

[ recap: my problem is that on a dual Xeon workstation running XP SP2,
  loading cygwin1.dll seems to crash out with a segfault about 99% of
  the time, but once I can get an instance of any cygwin program going,
  everything works fine after that ]

I've finally gotten a chance to look at this again.  I downloaded the
current snapshot (cygwin-inst-20041227) and tried running 'mount' from
that package under gdb.  The backtrace does not seem helpful, however:

> (gdb) run
> Starting program: /c/scratch/usr/bin/mount.exe
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to thread 5496.0x15e8]
> 0x7c810858 in KERNEL32!CreateThread () from /c/WINDOWS/system32/kernel32.dll
> (gdb) backtrace
> #0  0x7c810858 in KERNEL32!CreateThread ()
>    from /c/WINDOWS/system32/kernel32.dll


-- Dave

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -