To: cygwin AT cygwin DOT com
From: Heiko Elger <heiko_elger AT arburg DOT com>
Subject: find in root (/) results in stack trace
Date: Wed, 1 Feb 2012 12:57:29 +0000 (UTC)
Lines: 41
Message-ID: <loom.20120201T135424-360@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Hello,

I'm using the latest snapshot.

$ uname -a
CYGWIN_NT-6.1-WOW64 PCFX061 1.7.10s(0.259/5/3) 20120201 05:28:17 i686 Cygwin

Rebaseall and peflagsall are done.

Executing "find ." in the root will force a stack trace.

******* snip snip snip ****************
ente59 AT PCFX061 /
$ find . >/tmp/find.log
      0 [main] find 8996 C:\Programme\cygwinTest\bin\find.exe: *** fatal 
error - cwcsdup would have returned NULL
Stack trace:
Frame     Function  Args
0028B4D8  6102F96B  (0028B4D8, 00000000, 00000000, 20039A30)
0028B7C8  6102F96B  (6119BD20, 00008000, 00000000, 6119DB0F)
0028C7F8  61005F0C  (611CC458, 0028C824, 6228FE64, 00000000)
0028C818  61005F48  (611CC458, 00000000, FFFFFFFF, 6228FE64)
End of stack trace
Hangup
******* snip snip snip ****************

I noticed the problem yesterday with snapshot 2012-01-11.
I reproduced it 2012-01-23 and latest snapshot from today 2012-02-01.

I checked this at home on my two private computers running Win XP and Win7 
Ultimite (non 64bit version) with snapshot 2012-01-23
and I cannot reprodue the error.

So perhaps it seems to be a 64bit problem!

Can anyone agree reproducing same problem?

With best regards

Heiko Elger


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