From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: cygwin@cygwin.com
Subject: Re: 64-bit emacs crashes a lot
Date: Sat, 27 Jul 2013 04:42:00 -0000 [thread overview]
Message-ID: <51F33F52.4060405@cs.utoronto.ca> (raw)
In-Reply-To: <51F33565.1090406@cornell.edu>
On 26/07/2013 10:50 PM, Ken Brown wrote:
> On 7/26/2013 8:32 PM, Ryan Johnson wrote:
>> Hi all,
>>
>> Running 64-bit cygwin 1.7.22(0.268/5/3), with emacs-nox 24.3-4 inside
>> mintty 1.2-beta1-1, I keep getting seg faults and "Fatal error 6:
>> Aborted"
>> It happens at strange times, invariably during I/O of some kind (either
>> keyboard input or output from some compilation window); I don't get the
>> impression it's fork-related. I don't know how to get a backtrace from
>> emacs, given the way any exception or signal always loses the "userland"
>> stack (suggestions welcome).
>>
>> Anyone else seeing this?
>
> This doesn't really answer your question since I don't use emacs-nox,
> but I've been running 64-bit emacs-X11 and finding it very stable. I
> typically keep it running for several days at a time.
>
> You say you don't know how to get a backtrace from emacs. I assume
> you've installed emacs-debuginfo and run emacs under gdb. Are you
> saying you can never get a backtrace after it crashes?
I do have the emacs-debuginfo. I meant that the stack dump didn't have
any emacs frames in it (they were all cygwin1.dll), and my experience
with cygwin/gdb is that once you've taken a signal or exception you lose
the cygwin stack and just see a bunch of threads mucking around in
various low-level Windows dlls.
I have tried attaching gdb to emacs and setting a breakpoint on abort(),
but it didn't catch anything yet. I'm also hampered by gdb constantly
getting confused, breaking partway into emacs, and having to
detach/reattach it. I've started a new thread for that issue.
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
next prev parent reply other threads:[~2013-07-27 3:32 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 2:50 Ryan Johnson
2013-07-27 3:29 ` Ken Brown
2013-07-27 4:42 ` Ryan Johnson [this message]
2013-08-02 2:47 ` Ryan Johnson
2013-08-02 8:02 ` Corinna Vinschen
2013-08-02 11:04 ` Ken Brown
2013-08-02 12:07 ` Ryan Johnson
2013-08-03 19:05 ` Ryan Johnson
2013-08-03 20:13 ` Paul Allen
2013-08-05 15:00 ` Ken Brown
2013-08-05 15:30 ` Ryan Johnson
2013-08-08 17:43 ` Ken Brown
2013-08-08 18:01 ` Ryan Johnson
2013-08-10 3:29 ` Ryan Johnson
2013-08-10 13:59 ` Ken Brown
2013-08-10 15:25 ` Ryan Johnson
2013-08-10 18:01 ` Ken Brown
2013-08-14 14:04 ` Ryan Johnson
2013-08-14 14:07 ` Ryan Johnson
2013-08-15 12:32 ` Ryan Johnson
2013-08-15 16:58 ` Ken Brown
2013-08-15 17:11 ` Eli Zaretskii
2013-08-15 20:55 ` Ryan Johnson
2013-08-15 21:14 ` Ken Brown
2013-08-15 21:25 ` Ryan Johnson
2013-08-15 21:58 ` Ken Brown
2013-08-15 22:02 ` Ken Brown
2013-08-15 22:48 ` Ryan Johnson
2013-08-15 23:07 ` Ken Brown
2013-08-16 0:58 ` Ryan Johnson
2013-08-16 2:00 ` Ken Brown
2013-08-15 23:14 ` Ryan Johnson
2013-08-15 23:41 ` Ken Brown
2013-08-16 1:51 ` Ryan Johnson
2013-08-15 22:39 ` Ryan Johnson
2013-08-15 22:51 ` Ken Brown
2013-08-16 2:35 ` Ken Brown
2013-08-16 4:34 ` Ryan Johnson
2013-08-16 5:59 ` Ryan Johnson
2013-08-16 9:12 ` Eli Zaretskii
2013-08-16 11:33 ` Ryan Johnson
2013-08-16 8:59 ` Eli Zaretskii
2013-08-16 8:56 ` Eli Zaretskii
2013-08-16 9:07 ` Bengt Larsson
2013-08-11 16:50 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F33F52.4060405@cs.utoronto.ca \
--to=ryan.johnson@cs.utoronto.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).