Random fork failures

Yoni Londner yonihola2@gmail.com
Mon Jul 11 09:43:00 GMT 2011


> I did a little investigation - when the process hangs, I took the
> backtrace with process explorer.
> Process explorer does not know anything about cygwin debug symbols, so
> it just give an arbitrary func + offset.
> Then I used gdb to find out the real function: sync_proc_pipe doing
> yield in an endless loop.
>
Just to complete the mail, This is the stack as I get from process 
explorer (with my additions at cygwin1.dll frames):

ntkrnlpa.exe!KeSetEvent+0x2a1
ntkrnlpa.exe!KeDelayExecutionThread+0x5cc
ntkrnlpa.exe!KeWaitForMutexObject+0x393
ntkrnlpa.exe!KiDeliverApc+0x664
halmacpi.dll!KfRaiseIrql+0xcb
halmacpi.dll!KeRaiseIrqlToSynchLevel+0x8f
halmacpi.dll!HalEndSystemInterrupt+0x67
halmacpi.dll!HalInitializeProcessor+0xae8
ntkrnlpa.exe!ZwYieldExecution+0xabd
ntdll.dll!KiFastSystemCallRet
autochk.exe+0x5bcbc
ntdll.dll!KiFastSystemCallRet
cygwin1.dll!abort+0x79bc (0x610cdebc <spawn_guts+6188>)
cygwin1.dll!abort+0x805f (0x610ce55f <spawnve+255>)
cygwin1.dll!getenv+0x5fef (0x61029dbf <execvp+223>)
_test.exe+0x973e
_test.exe+0x9803
_test.exe+0x9961
_test.exe+0x14d4
_test.exe+0x15ce
cygwin1.dll!dll_crt0__FP11per_process+0x708
cygwin1.dll!setprogname+0x32a6
cygwin1.dll!setprogname+0x334b
_test.exe+0x47432
_test.exe+0x101a
kernel32.dll!BaseThreadInitThunk+0x12
ntdll.dll!RtlInitializeExceptionChain+0xef
ntdll.dll!RtlInitializeExceptionChain+0xc2

--
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



More information about the Cygwin mailing list