> Date: Thu, 10 Aug 2006 09:30:06 -0400 > From: "Ping Liang" <[EMAIL PROTECTED]> > Cc: [email protected] > > [Switching to thread 3340.0xe18] > (gdb) bt > #0 0x7c901231 in ntdll!DbgUiConnectToDbg () > from /cygdrive/c/WINDOWS/system32/ntdll.dll > #1 0x7c9507a8 in ntdll!KiIntSystemCall () > from /cygdrive/c/WINDOWS/system32/ntdll.dll > #2 0x00000005 in ?? () > #3 0x00000004 in ?? () > #4 0x00000001 in ?? () > #5 0x1873ffd0 in ?? () > #6 0x00000246 in ?? () > #7 0xffffffff in ?? () > #8 0x7c90ee18 in strchr () from /cygdrive/c/WINDOWS/system32/ntdll.dll > #9 0x7c9507c8 in ntdll!KiIntSystemCall () > from /cygdrive/c/WINDOWS/system32/ntdll.dll > #10 0x00000000 in ?? () > (gdb)
Thanks. This shows that Emacs was in a system call when you stopped it. You should now use the technique described in etc/DEBUG to find out where it is looping. Search for the section in DEBUG named "If the symptom of the bug is that Emacs fails to respond", and use the `finish' command as described there to find out where in the Emacs sources it loops. _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
