On Wed, Apr 28, 2004 at 01:44:01PM -0700, Peter A. Castro wrote: >On Wed, 28 Apr 2004, Daniel Clausen wrote: > >> Hi > >Greetings, Daniel, > >> On Tuesday, April 27, 2004, at 05:55PM, Dave Korn <[EMAIL PROTECTED]> wrote: >> >> [snip] > >This is a rather interesting problem. It appears that this is, yet >another, variation on the fork() & signal handling problem. Something >we thought had been resolved in a snapshot a while ago. If I run your >little test with 'tree 4 4', then run the little cp script, I get >differing results, both if I re-run it and if I change "$line.1" to >"$line.xx". You'll notice that when the hang happens, it's usually >*after* the cp runs. A quick check of the shell's state shows it's >sitting in severals waits, some of which I'm not quite sure of why they >are there:
This sure looks like a backtrace from an optimized, stripped Cygwin DLL. It is not too surprising if you get odd data from that. cgf >(gdb) thread 1 >[Switching to thread 1 (thread 258.0x10b)]#0 0x77f682cb in >ntdll!ZwWaitForMultipleObjects () from /d/WINNT/System32/NTDLL.DLL >(gdb) bt >#0 0x77f682cb in ntdll!ZwWaitForMultipleObjects () > from /d/WINNT/System32/NTDLL.DLL >#1 0x77f1ce6b in WaitForMultipleObjectsEx () > from /d/WINNT/system32/KERNEL32.DLL >#2 0x77f1cd76 in WaitForMultipleObjects () > from /d/WINNT/system32/KERNEL32.DLL >#3 0x610a5160 in cygwin1!__getreent () from /usr/bin/cygwin1.dll >#4 0x0022ebd0 in ?? () -- 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/
