$ ./gdb --pid 1048
GNU gdb (GDB) 220.127.116.1100202
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "mingw32".
For bug reporting instructions, please see:
Attaching to process 1048
[New Thread 1048.0x31c]
[New Thread 1048.0x85c]
Reading symbols from C:\cygwin\home\udalrich\emacs\emacs-23.1\bin\emacs.exe...do
[Switching to Thread 1048.0x85c]
(gdb) info thread
* 2 Thread 1048.0x85c 0x7c90120f in ntdll!DbgUiConnectToDbg ()
1 Thread 1048.0x31c 0x7c90e514 in ntdll!LdrAccessResource ()
(gdb) thread 1
[Switching to thread 1 (Thread 1048.0x31c)]#0 0x7c90e514 in ntdll!LdrAccessReso
urce () from C:\WINDOWS\system32\ntdll.dll
#0 0x7c90e514 in ntdll!LdrAccessResource ()
#1 0x7c90df5a in ntdll!ZwWaitForSingleObject ()
#2 0x7c8025db in WaitForSingleObjectEx ()
#3 0x00000749 in ?? ()
#4 0x00000000 in ?? ()
I don't think that's much more useful.
If I run it from gdb, it hangs. C-c will give me a gdb prompt. From there, where gives me the same stack trace as above. I suspect the ?? in the stack trace are due to emacs not being compiled with debug info. (I assume that's how the standard distribution is built.)