This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 64-bit emacs crashes a lot
- From: Ryan Johnson <ryan dot johnson at cs dot utoronto dot ca>
- To: cygwin at cygwin dot com
- Date: Wed, 14 Aug 2013 10:07:48 -0400
- Subject: Re: 64-bit emacs crashes a lot
- References: <51F3151D dot 7040000 at cs dot utoronto dot ca> <51F33565 dot 1090406 at cornell dot edu> <51F33F52 dot 4060405 at cs dot utoronto dot ca> <51FB1D9E dot 5090102 at cs dot utoronto dot ca> <20130802080211 dot GA18054 at calimero dot vinschen dot de> <51FB9228 dot 2020309 at cornell dot edu> <51FBA100 dot 90005 at cs dot utoronto dot ca> <51FD5462 dot 5020400 at cs dot utoronto dot ca> <51FFBDFF dot 7040501 at cornell dot edu> <51FFC4F2 dot 8080909 at cs dot utoronto dot ca> <5203D89E dot 6030801 at cornell dot edu> <5203DCCA dot 1010105 at cs dot utoronto dot ca> <5205B364 dot 8090007 at cs dot utoronto dot ca> <52064730 dot 50404 at cornell dot edu> <52065B3C dot 6060104 at cs dot utoronto dot ca> <52067FDD dot 4000708 at cornell dot edu> <520B8E7F dot 6060709 at cs dot utoronto dot ca>
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