> Date: Wed, 9 Aug 2006 22:50:44 -0400 > From: "Ping Liang" <[EMAIL PROTECTED]> > > Sorry it takes this long to reply. When I ran it under gdb, control-c > wouldn't break it. I ended up getting out by killing the process itself > (took 40% cpu). So I couldn't do bt. > > Any other hint, please?
There's no way to debug this except if we can interrupt Emacs when it's looping. I don't know how to do that, since I don't use Cygwin. Please ask on the Cygwin mailing list how to interrupt a Cygwin program when it runs under GDB; perhaps you can use the `kill' command, if you have its Cygwin port installed. Another possibility is to run Emacs outside GDB, and when it starts looping invoke GDB as "gdb -p PID", where PID is the Emacs process ID number. If that succeeds, it will stop Emacs, and you should then be able to do a backtrace. And please don't remove the mailing list from the CC header, I'd like to keep this discussion on the list so that others could contribute ideas. _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
