Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Wed, 4 Jul 2001 11:43:05 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: problem with 20010701 snapshot
Message-ID: <20010704114305.A7053@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <5564-Wed04Jul2001160307+0100-starksb AT ebi DOT ac DOT uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <5564-Wed04Jul2001160307+0100-starksb@ebi.ac.uk>; from starksb@ebi.ac.uk on Wed, Jul 04, 2001 at 04:03:07PM +0100

On Wed, Jul 04, 2001 at 04:03:07PM +0100, David Starks-Browning wrote:
>I have a big problem with the latest snapshot (20010701).  I don't
>have much to report, but I thought I should make it known, in case
>it's news.
>
>Background:
>
>	On NT4, just yesterday I updated to the latest net release.  I
>	had been using quite an old release, but most things worked,
>	and I didn't want to risk breaking anything -- it's my office
>	machine.  I upgraded out of obligation as FAQ maintainer, so I
>	could look at my own installation as a reference.
>
>	Once I restored my configuration details (/etc/passwd
>	containing a custom domain login id, for example), I was able
>	to login just fine.
>
>	I haven't been able to get /usr/bin/rsync working though, which
>	motivated me to try the latest snapshot.
>
>Upon installing
>cygwin-inst-20010701.tar.bz2, when trying to telnet in, I get:
>
>> starksb AT mozart$ telnet bryce.dhcp
>> Trying 193.62.198.162...
>> Connected to bryce.dhcp.ebi.ac.uk.
>> Escape character is '^]'.
>> 
>> CYGWIN_NT-4.0 1.3.3s(0.40/3/2) (bryce) (tty2)
>> 
>> login: starksb
>> Password:
>> 3610146 [main] login 285 open_stackdumpfile: Dumping stack trace to login.exe.stackdump
>> Connection closed by foreign host.
>
>Here is C:\WINNT\system32\login.exe.stackdump on bryce.dhcp:
>
>> Exception: STATUS_ACCESS_VIOLATION at eip=61082720
>> eax=00000002 ebx=0240F2B4 ecx=0240F2B6 edx=00000000 esi=0240F094 edi=0240F2B4
>> ebp=0240ED7C esp=0240ED70 program=C:\cygwin\bin\login.exe
>> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
>> Stack trace:
>> Frame     Function  Args
>> 0240ED7C  61082720  (0240F2B6, 00000000, 00000008, 1A025F08)
>> 0240EDAC  610825A3  (0240F2B4, 00000000, 0240F624, 0240F624)

In general, stack dumps are meaningless unless you have a debugging version
of the DLL with which you can match addresses and symbols.

The best way to track this down is to build your own version of the DLL and
then use either gdb or addr2line to figure out where the DLL is dying.

In gdb you can use 'l *0x61082720' to display the line.  With addr2line,
the syntax is:

	addr2line 0x61082720 -e /whereever/cygwin1.dll

cgf