On 14/08/2013 10:04 AM, Ryan Johnson wrote:
After a rash of crashes where I either forgot to attach gdb or forgot
to set appropriate breakpoints, I finally managed to catch the stack
trace below. It occurred during M-x compile, while emacs parsed the
compilation's rather copious output, which is by far the most common
type of crash I've been getting lately. I have no idea how to
interpret the backtrace, though.
False alarm... that backtrace was triggered by me attempting to
terminate the compile with C-c C-k, which emacs handled fine once gdb
let it continue.
Ryan
--
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
