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

Kiyo Kelvin Lee kiyolee@hotmail.com
Tue Jul 25 02:09:00 GMT 2006


Unfortunately, tested with 1.5.21-1 and snapshot 20060718 and with all 
latest packages (see updated cygcheck.out), both crashings and infinite 
loops are still happening. But now the problems look like independent of 
each other.

Infinite loops are not happening that often upon starting X Windows but 
they are constantly happening upon closing down X Windows. Usually the 
infinite loops are attached to one of the xterms or epist. But I haven't 
check if the infinite loops are exactly in the same place as before though.

So even with a clean start without infinite loops, crashings at the same 
place are still happening. And I have the feeling that they are 
happening more often with 1.5.21-1. And the error_start option does not 
seem to help and it does not seem to have any effect actually. One thing 
  is constant though, the crashings just aren't happening if I am not 
running X Windows.

Regards,
Kiyo

Christopher Faylor wrote:
> On Sun, Jul 23, 2006 at 03:55:05AM +1000, Kiyo Kelvin Lee wrote:
>> Now it seems the crashes are relating to another problem reported
>> earlier: 1.5.20: Occasionally infinite loop happens in do_exit()
>> (dcrt0.cc) (see attached original text below)
>>
>> I managed to make sure the infinite loop had not happened (more about
>> that later) and then tested to run configure for squid-2.6 multiple
>> times (ran for 2 hours) and was unable to reproduce a single crash.
>>
>> So I am guessing the infinite loop and hence explicitly killing the
>> offending process would leave cygwin in some funny state and lead to
>> those crashes.
> 
> If you can reproduce the crash with the latest snapshot then please
> try including
> 
> error_start:c:/cygwin/bin/gdb.exe
> 
> in your CYGWIN environment variable as I previously suggested.  This
> must be used before you start any other CYGWIN processes.
> 
> If it works, then it should be fairly easy to see what the state of
> cygwin is when the crash occurs.
> 
> FWIW, the loop in tty::terminate was reported as fixed in the latest
> snapshot.
> 
> cgf
> 

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cygcheck.out
URL: <http://cygwin.com/pipermail/cygwin/attachments/20060725/db84b86b/attachment.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/


More information about the Cygwin mailing list