Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 2 Dec 2004 09:36:21 -0500
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: A vexing installation problem
Message-ID: <20041202143621.GA28127@trixie.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
References: <20041129195946.GA4932@sonic.net> <6.2.0.14.0.20041129151309.046bfba0@pop.prospeed.net> <20041129215220.GA15085@sonic.net> <6.2.0.14.0.20041129171109.046d1728@pop.prospeed.net> <20041129231740.GA32760@sonic.net> <6.2.0.14.0.20041129181904.046bf960@pop.prospeed.net> <20041130011421.GA20359@sonic.net> <20041130170757.GA3861@sonic.net> <20041130192952.GA2722@sonic.net> <20041201184434.GA7909@sonic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20041201184434.GA7909@sonic.net>
User-Agent: Mutt/1.4.1i

On Wed, Dec 01, 2004 at 10:44:34AM -0800, David Hinds wrote:
>I've attached "strace" output from running "ls".  The output is
>slightly different from previous attempts, because I'd been able to
>run the postinstall scripts to populate /etc/passwd and /etc/group;
>but the failure mode appears unchanged, with death following shortly
>after signals are enabled.  The trace is still slightly variable from
>one run to the next; sometimes I get one or two messages about locks,
>sometimes not.
>
>**********************************************
>Program name: C:\local\cygwin\bin\ls.exe (1336)
>App version:  1005.0, api: 0.88
>DLL version:  1005.12, api: 0.116
>DLL build:    2004-11-10 08:34
>OS version:   Windows NT-5.1
>Heap size:    402653184
>Date/Time:    2004-12-01 10:27:38
>**********************************************

Nothing interesting there.

The snapshot 2004-12-01 snapshot was built with debugging enabled:

http://cygwin.com/snapshots/cygwin1-20041201.dll.bz2

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.

To debug cygwin:

1) Put the latest version of the dll which works for you
   in a directory "foo" along with a copy of gdb.exe.

2) Set the environment variable CYGWIN_TESTING=1 at the windows
   prompt.

3) Debug a cygwin application by typing:

   c:\foo\gdb /bin/pwd

   (do not cd to the foo directory here)

4) Type "run".

5) If you get a SEGV, it is possible that it is just a natural occurrence
   of calling BadWritePtr.  Type 'continue' a few times to make sure that
   the SEGV address does not change.

6) Type "backtrace" and report the results here.

cgf


--
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/