emacs child process goes defunct
Ken Brown
kbrown@cornell.edu
Fri Dec 7 03:43:00 GMT 2012
On 12/6/2012 5:20 PM, Rockefeller, Harry wrote:
> 'Emacs -Q' failed after a few minutes of doing svn file diffs.
Can you give me a detailed step-by-step recipe so that I can try to
reproduce the problem? I don't really know what you mean by "doing svn
file diffs".
> I ran gdb on the hung process. I am not too familiar with this
> kind of debugging.
> Let me know if there is more I can give next time this happens.
> Here is some output.
>
> ps
> PID PPID PGID WINPID TTY UID STIME COMMAND
> 8304 1 8304 8304 cons0 11097 15:35:35 /usr/bin/xterm
> 3032 8304 3032 8048 pty2 11097 15:35:42 /usr/bin/bash
> 6428 3032 3032 7580 pty2 11097 15:35:48 /usr/bin/xterm
> 6304 6428 6304 9440 pty3 11097 15:35:48 /usr/bin/bash
> 6120 6304 6120 10052 pty3 11097 15:42:55 /usr/bin/emacs-X11
> 7124 6120 7124 8524 ? 11097 16:02:29 /usr/bin/diff <defunct>
>
> And
>
> $ gdb --pid=6120
> GNU gdb (GDB) 7.5.50.20120815-cvs (cygwin-special)
> Copyright (C) 2012 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 "i686-cygwin".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Attaching to process 10052
> [New Thread 10052.0x2028]
> [New Thread 10052.0x2434]
> [New Thread 10052.0x1100]
> [New Thread 10052.0x78c]
> [New Thread 10052.0x225c]
> [New Thread 10052.0xca4]
> [New Thread 10052.0x2234]
> Reading symbols from /usr/bin/emacs-X11.exe...Reading symbols from /usr/lib/debug/usr/bin/emacs-X11.exe.dbg...done.
> done.
> (gdb) bt
> #0 0x7c90120f in ntdll!DbgUiConnectToDbg () from /cygdrive/c/WINDOWS/system32/ntdll.dll
> #1 0x7c952119 in ntdll!KiIntSystemCall () from /cygdrive/c/WINDOWS/system32/ntdll.dll
> #2 0x00000005 in ?? ()
> #3 0x00000000 in ?? ()
This is a backtrace of a thread that gdb has created. You need to
switch to thread 1 (the main emacs thread) before you can get a useful
backtrace:
(gdb) thread 1
(gdb) bt
Even better, you can get a backtrace of all threads with the command
`thread apply all bt' or, for more detail, `thread apply all bt full'.
And please attach cygcheck output when you write again.
Ken
--
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