1.5.20: Occasional crash at address 0x6100365f (cygthread::stub() in cygthread.cc)

[Kiyo Kelvin Lee]

Actually, I have 2 systems (one XP [AMD Athlon 64 3500] and one Win2K 
[Celeron 900]) both have the same problem and attached are the cygcheck 
output.

My sh.exe is bash.exe.

The crashes happen just sparsely and not upon all processes termination. 
When I ran, say, configure for openbox-2, I always got at least a few 
crashes but the configure procedure should have already ran hundreds of 
processes. Note the crashes did not seem to affect the configure 
procedure and configure finished just normally.

I tried to debug bash and get the stack trace with no success.
The crashing dialog is like attached to a ghost process. Click on CANCEL 
  does not start msdev.exe as the debugger. The dialog just gone.
Also tried to attach to a bash using gdb before running configure, the 
crashes still happen but gdb just couldn't catch anything, the bash just 
kept running (inside gdb).
Obviously, it is impossible (or is it not?) to attach gdb to all the 
processes got ran through the configure procedure.

Regards,
Kiyo

Christopher Faylor wrote:
> On Mon, Jul 10, 2006 at 04:51:21PM +1000, Kiyo Kelvin Lee wrote:
>> Using 1.5.20, occasionally sh.exe would crash with the standard Windows 
>> crash dialog with these information:
>>
>> [sh.exe - Application Error]
>> The instruction at "0x6100365f" referenced memory at "0x006cda90". The 
>> memory could not be "written".
>> Click on OK to terminate the program.
>> Click on CANCEL to debug the program.
>>
>> Tested snapshot 20060707 and the problem persists.
>>
>> With gdb, I found the address corresponding to the function 
>> cygthread:stub() of cygthread.cc (snapshot 20060707) at line 65:
>> 	_my_tls._ctinfo = info;
>>
>> Reported the problem before but, however, I hope the little further 
>> information can help resolving the problem.
> 
> Is /bin/sh.exe bash or ash on your system.
> 
> Also, could you include the cygcheck output as mentioned at
> http://cygwin.com/problems.html ?
> 
> I appreciate that you've taken the steps to debug this but without a way
> to duplicate the problem there isn't much that can be done.  I've run
> both bash and ash in every way I could think of to duplicate this
> problem with no success.  I'm stumped as to how and why a cygthread
> could be firing while a process is exiting.
> 
> If you can capture this state in gdb and get backtraces of all of the
> running threads, that would probably help.
> 
> cgf
> 

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: xp_cygcheck.out
URL: <http://cygwin.com/pipermail/cygwin/attachments/20060719/b7df2aa3/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: w2k_cygcheck.out
URL: <http://cygwin.com/pipermail/cygwin/attachments/20060719/b7df2aa3/attachment-0001.ksh>
-------------- next part --------------
--
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/