* sshd fork failure
@ 2012-08-30 21:59 marco atzeri
2012-10-13 15:39 ` Christopher Faylor
0 siblings, 1 reply; 10+ messages in thread
From: marco atzeri @ 2012-08-30 21:59 UTC (permalink / raw)
To: cygwin
Hi,
tracing the sshd process on latest cygwin shapshot ,
I see that the fork is failing due to exception C0000005
1 1 [main] sshd (4644)
**********************************************
5921 5922 [main] sshd (4644) Program name:
E:\cygwin\usr\sbin\sshd.exe (windows pid 4644)
30 5952 [main] sshd (4644) OS version: Windows NT-6.1
25 5977 [main] sshd (4644)
**********************************************
636 6613 [main] sshd (4644) sigprocmask: 0 = sigprocmask (0,
0x6123D428, 0x610FBB30)
122 6735 [main] sshd 4644 child_copy: cygheap - hp 0x20C low
0x612708D0, high 0x61277640, res 1
1368 8103 [main] sshd 4644 child_copy: done
--- Process 4644, exception C0000005 at 61137277
$ addr2line.exe 61137277 -e /usr/bin/cygwin1.dll
/netrel/src/cygwin-snapshot-20120827-1/newlib/libc/stdlib/mbtowc_r.c:323
that should be:
ch = (state->__count == 1) ? t[i++] : state->__value.__wchb[1];
inside __utf8_mbtowc .
It looks a strange place for a fork failure, but it is used in
winsup/cygwin/cygheap.cc so it could make sense.
Any suggestion how to follow/debug the child portion of fork ?
Marco
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sshd fork failure
2012-08-30 21:59 sshd fork failure marco atzeri
@ 2012-10-13 15:39 ` Christopher Faylor
2012-10-13 16:10 ` marco atzeri
0 siblings, 1 reply; 10+ messages in thread
From: Christopher Faylor @ 2012-10-13 15:39 UTC (permalink / raw)
To: cygwin
On Thu, Aug 30, 2012 at 06:44:39PM +0200, marco atzeri wrote:
>Hi,
>tracing the sshd process on latest cygwin shapshot ,
>I see that the fork is failing due to exception C0000005
>
> 1 1 [main] sshd (4644)
>**********************************************
> 5921 5922 [main] sshd (4644) Program name:
>E:\cygwin\usr\sbin\sshd.exe (windows pid 4644)
> 30 5952 [main] sshd (4644) OS version: Windows NT-6.1
> 25 5977 [main] sshd (4644)
>**********************************************
> 636 6613 [main] sshd (4644) sigprocmask: 0 = sigprocmask (0,
>0x6123D428, 0x610FBB30)
> 122 6735 [main] sshd 4644 child_copy: cygheap - hp 0x20C low
>0x612708D0, high 0x61277640, res 1
> 1368 8103 [main] sshd 4644 child_copy: done
>--- Process 4644, exception C0000005 at 61137277
>
>
>
>$ addr2line.exe 61137277 -e /usr/bin/cygwin1.dll
>/netrel/src/cygwin-snapshot-20120827-1/newlib/libc/stdlib/mbtowc_r.c:323
>
>that should be:
>
> ch = (state->__count == 1) ? t[i++] : state->__value.__wchb[1];
>
>inside __utf8_mbtowc .
>It looks a strange place for a fork failure, but it is used in
>winsup/cygwin/cygheap.cc so it could make sense.
>
>Any suggestion how to follow/debug the child portion of fork ?
Is this still failing? We're looking to release 1.7.17 soon.
cgf
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sshd fork failure
2012-10-13 15:39 ` Christopher Faylor
@ 2012-10-13 16:10 ` marco atzeri
2012-10-13 16:54 ` Christopher Faylor
0 siblings, 1 reply; 10+ messages in thread
From: marco atzeri @ 2012-10-13 16:10 UTC (permalink / raw)
To: cygwin
On 10/13/2012 5:39 PM, Christopher Faylor wrote:
> On Thu, Aug 30, 2012 at 06:44:39PM +0200, marco atzeri wrote:
>> Hi,
>> tracing the sshd process on latest cygwin shapshot ,
>> I see that the fork is failing due to exception C0000005
>>
>> 1 1 [main] sshd (4644)
>> **********************************************
>> 5921 5922 [main] sshd (4644) Program name:
>> E:\cygwin\usr\sbin\sshd.exe (windows pid 4644)
>> 30 5952 [main] sshd (4644) OS version: Windows NT-6.1
>> 25 5977 [main] sshd (4644)
>> **********************************************
>> 636 6613 [main] sshd (4644) sigprocmask: 0 = sigprocmask (0,
>> 0x6123D428, 0x610FBB30)
>> 122 6735 [main] sshd 4644 child_copy: cygheap - hp 0x20C low
>> 0x612708D0, high 0x61277640, res 1
>> 1368 8103 [main] sshd 4644 child_copy: done
>> --- Process 4644, exception C0000005 at 61137277
>>
>>
>>
>> $ addr2line.exe 61137277 -e /usr/bin/cygwin1.dll
>> /netrel/src/cygwin-snapshot-20120827-1/newlib/libc/stdlib/mbtowc_r.c:323
>>
>> that should be:
>>
>> ch = (state->__count == 1) ? t[i++] : state->__value.__wchb[1];
>>
>> inside __utf8_mbtowc .
>> It looks a strange place for a fork failure, but it is used in
>> winsup/cygwin/cygheap.cc so it could make sense.
>>
>> Any suggestion how to follow/debug the child portion of fork ?
>
> Is this still failing? We're looking to release 1.7.17 soon.
>
> cgf
>
on 20121012 similar but in another location.
--- Process 6280, exception C0000005 at 61137DC8
427 147466 [main] sshd 6280 exception::handle: In
cygwin_except_handler exception 0xC0000005 at 0x61137DC8 sp 0x289270
67 147533 [main] sshd 6280 exception::handle: In
cygwin_except_handler signal 11 at 0x61137DC8
38 147571 [main] sshd 6280 exception::handle: In
cygwin_except_handler calling 0x0
37 147608 [main] sshd 6280 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
addr2line.exe 61137DC8 -e /usr/bin/cygwin1.dll
/netrel/src/cygwin-snapshot-20121012-1/newlib/libc/stdio/findfp.c:296
Marco
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sshd fork failure
2012-10-13 16:10 ` marco atzeri
@ 2012-10-13 16:54 ` Christopher Faylor
2012-10-13 18:21 ` marco atzeri
0 siblings, 1 reply; 10+ messages in thread
From: Christopher Faylor @ 2012-10-13 16:54 UTC (permalink / raw)
To: cygwin
On Sat, Oct 13, 2012 at 06:10:23PM +0200, marco atzeri wrote:
>On 10/13/2012 5:39 PM, Christopher Faylor wrote:
>> On Thu, Aug 30, 2012 at 06:44:39PM +0200, marco atzeri wrote:
>>> Hi,
>>> tracing the sshd process on latest cygwin shapshot ,
>>> I see that the fork is failing due to exception C0000005
>>>
>>> 1 1 [main] sshd (4644)
>>> **********************************************
>>> 5921 5922 [main] sshd (4644) Program name:
>>> E:\cygwin\usr\sbin\sshd.exe (windows pid 4644)
>>> 30 5952 [main] sshd (4644) OS version: Windows NT-6.1
>>> 25 5977 [main] sshd (4644)
>>> **********************************************
>>> 636 6613 [main] sshd (4644) sigprocmask: 0 = sigprocmask (0,
>>> 0x6123D428, 0x610FBB30)
>>> 122 6735 [main] sshd 4644 child_copy: cygheap - hp 0x20C low
>>> 0x612708D0, high 0x61277640, res 1
>>> 1368 8103 [main] sshd 4644 child_copy: done
>>> --- Process 4644, exception C0000005 at 61137277
>>>
>>>
>>>
>>> $ addr2line.exe 61137277 -e /usr/bin/cygwin1.dll
>>> /netrel/src/cygwin-snapshot-20120827-1/newlib/libc/stdlib/mbtowc_r.c:323
>>>
>>> that should be:
>>>
>>> ch = (state->__count == 1) ? t[i++] : state->__value.__wchb[1];
>>>
>>> inside __utf8_mbtowc .
>>> It looks a strange place for a fork failure, but it is used in
>>> winsup/cygwin/cygheap.cc so it could make sense.
>>>
>>> Any suggestion how to follow/debug the child portion of fork ?
>>
>> Is this still failing? We're looking to release 1.7.17 soon.
>
>on 20121012 similar but in another location.
>
>--- Process 6280, exception C0000005 at 61137DC8
> 427 147466 [main] sshd 6280 exception::handle: In
>cygwin_except_handler exception 0xC0000005 at 0x61137DC8 sp 0x289270
> 67 147533 [main] sshd 6280 exception::handle: In
>cygwin_except_handler signal 11 at 0x61137DC8
> 38 147571 [main] sshd 6280 exception::handle: In
>cygwin_except_handler calling 0x0
> 37 147608 [main] sshd 6280 exception::handle: Exception:
>STATUS_ACCESS_VIOLATION
>
> addr2line.exe 61137DC8 -e /usr/bin/cygwin1.dll
>/netrel/src/cygwin-snapshot-20121012-1/newlib/libc/stdio/findfp.c:296
You seem to be the only person reporting this problem. Everyone else
updates to a snapshot to cure ssh problems. FWIW, that instruction
shouldn't even be executed.
cgf
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sshd fork failure
2012-10-13 16:54 ` Christopher Faylor
@ 2012-10-13 18:21 ` marco atzeri
2012-10-13 18:25 ` Christopher Faylor
0 siblings, 1 reply; 10+ messages in thread
From: marco atzeri @ 2012-10-13 18:21 UTC (permalink / raw)
To: cygwin
On 10/13/2012 6:54 PM, Christopher Faylor wrote:
> On Sat, Oct 13, 2012 at 06:10:23PM +0200, marco atzeri wrote:
>> On 10/13/2012 5:39 PM, Christopher Faylor wrote:
>>> On Thu, Aug 30, 2012 at 06:44:39PM +0200, marco atzeri wrote:
>>>> Hi,
>>>> tracing the sshd process on latest cygwin shapshot ,
>>>> I see that the fork is failing due to exception C0000005
>>>>
>>>> 1 1 [main] sshd (4644)
>>>> **********************************************
>>>> 5921 5922 [main] sshd (4644) Program name:
>>>> E:\cygwin\usr\sbin\sshd.exe (windows pid 4644)
>>>> 30 5952 [main] sshd (4644) OS version: Windows NT-6.1
>>>> 25 5977 [main] sshd (4644)
>>>> **********************************************
>>>> 636 6613 [main] sshd (4644) sigprocmask: 0 = sigprocmask (0,
>>>> 0x6123D428, 0x610FBB30)
>>>> 122 6735 [main] sshd 4644 child_copy: cygheap - hp 0x20C low
>>>> 0x612708D0, high 0x61277640, res 1
>>>> 1368 8103 [main] sshd 4644 child_copy: done
>>>> --- Process 4644, exception C0000005 at 61137277
>>>>
>>>>
>>>>
>>>> $ addr2line.exe 61137277 -e /usr/bin/cygwin1.dll
>>>> /netrel/src/cygwin-snapshot-20120827-1/newlib/libc/stdlib/mbtowc_r.c:323
>>>>
>>>> that should be:
>>>>
>>>> ch = (state->__count == 1) ? t[i++] : state->__value.__wchb[1];
>>>>
>>>> inside __utf8_mbtowc .
>>>> It looks a strange place for a fork failure, but it is used in
>>>> winsup/cygwin/cygheap.cc so it could make sense.
>>>>
>>>> Any suggestion how to follow/debug the child portion of fork ?
>>>
>>> Is this still failing? We're looking to release 1.7.17 soon.
>>
>> on 20121012 similar but in another location.
>>
>> --- Process 6280, exception C0000005 at 61137DC8
>> 427 147466 [main] sshd 6280 exception::handle: In
>> cygwin_except_handler exception 0xC0000005 at 0x61137DC8 sp 0x289270
>> 67 147533 [main] sshd 6280 exception::handle: In
>> cygwin_except_handler signal 11 at 0x61137DC8
>> 38 147571 [main] sshd 6280 exception::handle: In
>> cygwin_except_handler calling 0x0
>> 37 147608 [main] sshd 6280 exception::handle: Exception:
>> STATUS_ACCESS_VIOLATION
>>
>> addr2line.exe 61137DC8 -e /usr/bin/cygwin1.dll
>> /netrel/src/cygwin-snapshot-20121012-1/newlib/libc/stdio/findfp.c:296
>
> You seem to be the only person reporting this problem. Everyone else
> updates to a snapshot to cure ssh problems. FWIW, that instruction
> shouldn't even be executed.
>
> cgf
>
I have such issue only on sshd forking and for long time,
so it is not relative to last snapshots.
As this the is only program that involve several USER accounts
I suspect some crippling "corporate" group policy or a very
strange BLODA effect.
Marco
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sshd fork failure
2012-10-13 18:21 ` marco atzeri
@ 2012-10-13 18:25 ` Christopher Faylor
2012-10-13 19:22 ` marco atzeri
0 siblings, 1 reply; 10+ messages in thread
From: Christopher Faylor @ 2012-10-13 18:25 UTC (permalink / raw)
To: cygwin
On Sat, Oct 13, 2012 at 08:21:01PM +0200, marco atzeri wrote:
>On 10/13/2012 6:54 PM, Christopher Faylor wrote:
>> On Sat, Oct 13, 2012 at 06:10:23PM +0200, marco atzeri wrote:
>>> On 10/13/2012 5:39 PM, Christopher Faylor wrote:
>>>> On Thu, Aug 30, 2012 at 06:44:39PM +0200, marco atzeri wrote:
>>>>> Hi,
>>>>> tracing the sshd process on latest cygwin shapshot ,
>>>>> I see that the fork is failing due to exception C0000005
>>>>>
>>>>> 1 1 [main] sshd (4644)
>>>>> **********************************************
>>>>> 5921 5922 [main] sshd (4644) Program name:
>>>>> E:\cygwin\usr\sbin\sshd.exe (windows pid 4644)
>>>>> 30 5952 [main] sshd (4644) OS version: Windows NT-6.1
>>>>> 25 5977 [main] sshd (4644)
>>>>> **********************************************
>>>>> 636 6613 [main] sshd (4644) sigprocmask: 0 = sigprocmask (0,
>>>>> 0x6123D428, 0x610FBB30)
>>>>> 122 6735 [main] sshd 4644 child_copy: cygheap - hp 0x20C low
>>>>> 0x612708D0, high 0x61277640, res 1
>>>>> 1368 8103 [main] sshd 4644 child_copy: done
>>>>> --- Process 4644, exception C0000005 at 61137277
>>>>>
>>>>>
>>>>>
>>>>> $ addr2line.exe 61137277 -e /usr/bin/cygwin1.dll
>>>>> /netrel/src/cygwin-snapshot-20120827-1/newlib/libc/stdlib/mbtowc_r.c:323
>>>>>
>>>>> that should be:
>>>>>
>>>>> ch = (state->__count == 1) ? t[i++] : state->__value.__wchb[1];
>>>>>
>>>>> inside __utf8_mbtowc .
>>>>> It looks a strange place for a fork failure, but it is used in
>>>>> winsup/cygwin/cygheap.cc so it could make sense.
>>>>>
>>>>> Any suggestion how to follow/debug the child portion of fork ?
>>>>
>>>> Is this still failing? We're looking to release 1.7.17 soon.
>>>
>>> on 20121012 similar but in another location.
>>>
>>> --- Process 6280, exception C0000005 at 61137DC8
>>> 427 147466 [main] sshd 6280 exception::handle: In
>>> cygwin_except_handler exception 0xC0000005 at 0x61137DC8 sp 0x289270
>>> 67 147533 [main] sshd 6280 exception::handle: In
>>> cygwin_except_handler signal 11 at 0x61137DC8
>>> 38 147571 [main] sshd 6280 exception::handle: In
>>> cygwin_except_handler calling 0x0
>>> 37 147608 [main] sshd 6280 exception::handle: Exception:
>>> STATUS_ACCESS_VIOLATION
>>>
>>> addr2line.exe 61137DC8 -e /usr/bin/cygwin1.dll
>>> /netrel/src/cygwin-snapshot-20121012-1/newlib/libc/stdio/findfp.c:296
>>
>> You seem to be the only person reporting this problem. Everyone else
>> updates to a snapshot to cure ssh problems. FWIW, that instruction
>> shouldn't even be executed.
>
>I have such issue only on sshd forking and for long time,
>so it is not relative to last snapshots.
Corinna fixed an issue which could have manifested as ssh SIGSEGVing.
Given the fact that the 61137DC8 doesn't make any sense, are you sure
you're actually using a snapshot? Could there be an old version of
cygwin1.dll sitting around somewhere?
cgf
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sshd fork failure
2012-10-13 18:25 ` Christopher Faylor
@ 2012-10-13 19:22 ` marco atzeri
2012-10-13 19:26 ` Christopher Faylor
0 siblings, 1 reply; 10+ messages in thread
From: marco atzeri @ 2012-10-13 19:22 UTC (permalink / raw)
To: cygwin
On 10/13/2012 8:24 PM, Christopher Faylor wrote:
> On Sat, Oct 13, 2012 at 08:21:01PM +0200, marco atzeri wrote:
>> On 10/13/2012 6:54 PM, Christopher Faylor wrote:
>>> On Sat, Oct 13, 2012 at 06:10:23PM +0200, marco atzeri wrote:
>>>> On 10/13/2012 5:39 PM, Christopher Faylor wrote:
>>>>> On Thu, Aug 30, 2012 at 06:44:39PM +0200, marco atzeri wrote:
>>>>>> Hi,
>>>>>> tracing the sshd process on latest cygwin shapshot ,
>>>>>> I see that the fork is failing due to exception C0000005
>>>>>>
>>>>>> 1 1 [main] sshd (4644)
>>>>>> **********************************************
>>>>>> 5921 5922 [main] sshd (4644) Program name:
>>>>>> E:\cygwin\usr\sbin\sshd.exe (windows pid 4644)
>>>>>> 30 5952 [main] sshd (4644) OS version: Windows NT-6.1
>>>>>> 25 5977 [main] sshd (4644)
>>>>>> **********************************************
>>>>>> 636 6613 [main] sshd (4644) sigprocmask: 0 = sigprocmask (0,
>>>>>> 0x6123D428, 0x610FBB30)
>>>>>> 122 6735 [main] sshd 4644 child_copy: cygheap - hp 0x20C low
>>>>>> 0x612708D0, high 0x61277640, res 1
>>>>>> 1368 8103 [main] sshd 4644 child_copy: done
>>>>>> --- Process 4644, exception C0000005 at 61137277
>>>>>>
>>>>>>
>>>>>>
>>>>>> $ addr2line.exe 61137277 -e /usr/bin/cygwin1.dll
>>>>>> /netrel/src/cygwin-snapshot-20120827-1/newlib/libc/stdlib/mbtowc_r.c:323
>>>>>>
>>>>>> that should be:
>>>>>>
>>>>>> ch = (state->__count == 1) ? t[i++] : state->__value.__wchb[1];
>>>>>>
>>>>>> inside __utf8_mbtowc .
>>>>>> It looks a strange place for a fork failure, but it is used in
>>>>>> winsup/cygwin/cygheap.cc so it could make sense.
>>>>>>
>>>>>> Any suggestion how to follow/debug the child portion of fork ?
>>>>>
>>>>> Is this still failing? We're looking to release 1.7.17 soon.
>>>>
>>>> on 20121012 similar but in another location.
>>>>
>>>> --- Process 6280, exception C0000005 at 61137DC8
>>>> 427 147466 [main] sshd 6280 exception::handle: In
>>>> cygwin_except_handler exception 0xC0000005 at 0x61137DC8 sp 0x289270
>>>> 67 147533 [main] sshd 6280 exception::handle: In
>>>> cygwin_except_handler signal 11 at 0x61137DC8
>>>> 38 147571 [main] sshd 6280 exception::handle: In
>>>> cygwin_except_handler calling 0x0
>>>> 37 147608 [main] sshd 6280 exception::handle: Exception:
>>>> STATUS_ACCESS_VIOLATION
>>>>
>>>> addr2line.exe 61137DC8 -e /usr/bin/cygwin1.dll
>>>> /netrel/src/cygwin-snapshot-20121012-1/newlib/libc/stdio/findfp.c:296
>>>
>>> You seem to be the only person reporting this problem. Everyone else
>>> updates to a snapshot to cure ssh problems. FWIW, that instruction
>>> shouldn't even be executed.
>>
>> I have such issue only on sshd forking and for long time,
>> so it is not relative to last snapshots.
>
> Corinna fixed an issue which could have manifested as ssh SIGSEGVing.
> Given the fact that the 61137DC8 doesn't make any sense, are you sure
> you're actually using a snapshot? Could there be an old version of
> cygwin1.dll sitting around somewhere?
>
> cgf
>
$ uname -a
CYGWIN_NT-6.1-WOW64 MARCOATZERI 1.7.17s(0.262/5/3) 20121012 01:20:45
i686 Cygwin
could be that the cygwin1.dbg of 20121012 is not correct ?
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sshd fork failure
2012-10-13 19:22 ` marco atzeri
@ 2012-10-13 19:26 ` Christopher Faylor
2012-10-13 21:05 ` marco atzeri
0 siblings, 1 reply; 10+ messages in thread
From: Christopher Faylor @ 2012-10-13 19:26 UTC (permalink / raw)
To: cygwin
On Sat, Oct 13, 2012 at 09:21:52PM +0200, marco atzeri wrote:
>On 10/13/2012 8:24 PM, Christopher Faylor wrote:
>> On Sat, Oct 13, 2012 at 08:21:01PM +0200, marco atzeri wrote:
>>> On 10/13/2012 6:54 PM, Christopher Faylor wrote:
>>>> On Sat, Oct 13, 2012 at 06:10:23PM +0200, marco atzeri wrote:
>>>>> On 10/13/2012 5:39 PM, Christopher Faylor wrote:
>>>>>> On Thu, Aug 30, 2012 at 06:44:39PM +0200, marco atzeri wrote:
>>>>>>> Hi,
>>>>>>> tracing the sshd process on latest cygwin shapshot ,
>>>>>>> I see that the fork is failing due to exception C0000005
>>>>>>>
>>>>>>> 1 1 [main] sshd (4644)
>>>>>>> **********************************************
>>>>>>> 5921 5922 [main] sshd (4644) Program name:
>>>>>>> E:\cygwin\usr\sbin\sshd.exe (windows pid 4644)
>>>>>>> 30 5952 [main] sshd (4644) OS version: Windows NT-6.1
>>>>>>> 25 5977 [main] sshd (4644)
>>>>>>> **********************************************
>>>>>>> 636 6613 [main] sshd (4644) sigprocmask: 0 = sigprocmask (0,
>>>>>>> 0x6123D428, 0x610FBB30)
>>>>>>> 122 6735 [main] sshd 4644 child_copy: cygheap - hp 0x20C low
>>>>>>> 0x612708D0, high 0x61277640, res 1
>>>>>>> 1368 8103 [main] sshd 4644 child_copy: done
>>>>>>> --- Process 4644, exception C0000005 at 61137277
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> $ addr2line.exe 61137277 -e /usr/bin/cygwin1.dll
>>>>>>> /netrel/src/cygwin-snapshot-20120827-1/newlib/libc/stdlib/mbtowc_r.c:323
>>>>>>>
>>>>>>> that should be:
>>>>>>>
>>>>>>> ch = (state->__count == 1) ? t[i++] : state->__value.__wchb[1];
>>>>>>>
>>>>>>> inside __utf8_mbtowc .
>>>>>>> It looks a strange place for a fork failure, but it is used in
>>>>>>> winsup/cygwin/cygheap.cc so it could make sense.
>>>>>>>
>>>>>>> Any suggestion how to follow/debug the child portion of fork ?
>>>>>>
>>>>>> Is this still failing? We're looking to release 1.7.17 soon.
>>>>>
>>>>> on 20121012 similar but in another location.
>>>>>
>>>>> --- Process 6280, exception C0000005 at 61137DC8
>>>>> 427 147466 [main] sshd 6280 exception::handle: In
>>>>> cygwin_except_handler exception 0xC0000005 at 0x61137DC8 sp 0x289270
>>>>> 67 147533 [main] sshd 6280 exception::handle: In
>>>>> cygwin_except_handler signal 11 at 0x61137DC8
>>>>> 38 147571 [main] sshd 6280 exception::handle: In
>>>>> cygwin_except_handler calling 0x0
>>>>> 37 147608 [main] sshd 6280 exception::handle: Exception:
>>>>> STATUS_ACCESS_VIOLATION
>>>>>
>>>>> addr2line.exe 61137DC8 -e /usr/bin/cygwin1.dll
>>>>> /netrel/src/cygwin-snapshot-20121012-1/newlib/libc/stdio/findfp.c:296
>>>>
>>>>You seem to be the only person reporting this problem. Everyone else
>>>>updates to a snapshot to cure ssh problems. FWIW, that instruction
>>>>shouldn't even be executed.
>>>
>>>I have such issue only on sshd forking and for long time, so it is not
>>>relative to last snapshots.
>>
>>Corinna fixed an issue which could have manifested as ssh SIGSEGVing.
>>Given the fact that the 61137DC8 doesn't make any sense, are you sure
>>you're actually using a snapshot? Could there be an old version of
>>cygwin1.dll sitting around somewhere?
>
>$ uname -a CYGWIN_NT-6.1-WOW64 MARCOATZERI 1.7.17s(0.262/5/3) 20121012 01:20:45 i686 Cygwin
That doesn't show anything other than the fact that uname is
sitting next to a snapshot cygwin1.dll.
>could be that the cygwin1.dbg of 20121012 is not correct ?
No. This has nothing to do with cygwin1.dbg. The address 61137DC8 is
in the middle of an instruction.
cgf
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sshd fork failure
2012-10-13 19:26 ` Christopher Faylor
@ 2012-10-13 21:05 ` marco atzeri
2012-10-13 21:17 ` Gregory M. Turner
0 siblings, 1 reply; 10+ messages in thread
From: marco atzeri @ 2012-10-13 21:05 UTC (permalink / raw)
To: cygwin
On 10/13/2012 9:26 PM, Christopher Faylor wrote:
>
> No. This has nothing to do with cygwin1.dbg. The address 61137DC8 is
> in the middle of an instruction.
>
> cgf
>
after a second rebaseall and a full updatedb to look for any
other cygwin1.dll, now sshd is working as expected.
It does not make sense.....
waiting to see 1.7.17
Thanks
Marco
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sshd fork failure
2012-10-13 21:05 ` marco atzeri
@ 2012-10-13 21:17 ` Gregory M. Turner
0 siblings, 0 replies; 10+ messages in thread
From: Gregory M. Turner @ 2012-10-13 21:17 UTC (permalink / raw)
To: cygwin
On 10/13/2012 2:04 PM, marco atzeri wrote:
> On 10/13/2012 9:26 PM, Christopher Faylor wrote:
>
>>
>> No. This has nothing to do with cygwin1.dbg. The address 61137DC8 is
>> in the middle of an instruction.
>>
>> cgf
>>
>
> after a second rebaseall and a full updatedb to look for any
> other cygwin1.dll, now sshd is working as expected.
>
> It does not make sense.....
>
> waiting to see 1.7.17
Sensibly or not, these base-address issues can be quite intermittent --
remember that cygwin is not the only player in this drama.
I have several times seen repeatable cycles of fork failures, where
attempt #1 always fails, attempt #2 always succeeds, attempt #3 always
fails, and so on.
-gmt
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2012-10-13 21:17 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-08-30 21:59 sshd fork failure marco atzeri
2012-10-13 15:39 ` Christopher Faylor
2012-10-13 16:10 ` marco atzeri
2012-10-13 16:54 ` Christopher Faylor
2012-10-13 18:21 ` marco atzeri
2012-10-13 18:25 ` Christopher Faylor
2012-10-13 19:22 ` marco atzeri
2012-10-13 19:26 ` Christopher Faylor
2012-10-13 21:05 ` marco atzeri
2012-10-13 21:17 ` Gregory M. Turner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).