On Tue, Oct 14, 2003 at 05:28:41PM +0100, Steve Fairbairn wrote: >Just trying to either re-enforce or counter Brian's debug info, I have done >the same thing Chris requested of him with my hung cygpath process. > >(gdb) info threads > 3 thread 164.0xd88 0x77f75a59 in ntdll!DbgUiConnectToDbg () > from /cygdrive/c/WINDOWS/System32/ntdll.dll > 2 thread 164.0x118 0x7ffe0304 in ?? () >* 1 thread 164.0x124 0x7ffe0304 in ?? () > >Thread 1 >(gdb) l *0x61092939 >0x61092939 is in muto::acquire(unsigned long) >(../../../../src/winsup/cygwin/sync.cc:75). >(gdb) l *0x6108da76 >0x6108da76 is in WFMO (../../../../src/winsup/cygwin/sigproc.cc:1248). >(gdb) l *0x61092b50 >0x61092b50 is in close_all_files() >(../../../../src/winsup/cygwin/syscalls.cc:102). >(gdb) l *0x6108fffd >0x6108fffd is in spawn_guts(char const*, char const* const*, char const* >const*, int) (../../../../src/winsup/cygwin/spawn.cc:847).
This is roughly the same information that Brian provided. I'm still puzzled as to how it could come to pass. cgf -- 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/
