From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Emacs crashing on C-x C-g
Date: Thu, 25 Oct 2012 14:40:00 -0000 [thread overview]
Message-ID: <50894F58.6050000@cornell.edu> (raw)
In-Reply-To: <50885D17.9090101@cs.utoronto.ca>
On 10/24/2012 5:26 PM, Ryan Johnson wrote:
> On 24/10/2012 5:01 PM, Ken Brown wrote:
>> On 10/24/2012 9:09 AM, Ryan Johnson wrote:
>>> On 01/10/2012 4:08 PM, Ryan Johnson wrote:
>>> > On 01/10/2012 3:07 PM, Ken Brown wrote:
>>> >> On 10/1/2012 2:51 PM, Ryan Johnson wrote:
>>> >>> I'm hitting a strange behavior with emacs lately, where hitting
>>> >>> C-x C-g [1] sometimes causes it to quit instantly: no request to
>>> >>> save files, no seg fault, no error message, just gone (have to
>>> >>> reset the terminal to clear out emacs' ncurses settings). It
>>> >>> invariably happens after I've been away from the terminal for a
>>> >>> while (days) and then come back use it again.
>>> >>>
>>> >>> has anyone else had this happen to them?
>>> >> I haven't seen it, and I do leave emacs running for days or weeks.
>>> >> But I almost always run emacs under X, not in a terminal. Also, I
>>> >> generally use the latest Cygwin snapshot. Have you tried that?
>>> >> Maybe you're being bitten by the /etc problem that Corinna fixed in
>>> >> late July (http://cygwin.com/ml/cygwin/2012-07/msg00666.html).
>>> > OK, I'll give the snapshot a try when I get a chance.
>>>
>>> Rats. I thought it was working, but the problem just it again. This time
>>> the emacs session had just been created by a mercurial check-in (to edit
>>> the changelog message) and crashed when I hit C-g to cancel an ESC I no
>>> longer needed.
>
>>> This time the crash is reproducible, and the test case below paints an
>>> "interesting" story:
>
>>> EDITOR='emacs -q -nw' hg ci
>>> ESC C-g
>>> <<<crash>>>
>>> reset
>>> <<<"reset is control-G (^G).">>>
>>> EDITOR='emacs -q -nw' hg ci
>>> C-g
>>> <<<"interrupted!">>>
>>> reset -i ^c
>>> <<<no message>>>
>>> cat
>>> C-g
>>> <<<"Quit (core dumped)">>>
>
>> This looks like a known Emacs issue:
>>
>> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12697
>>
>> I imagine it will be fixed before the release of Emacs 24.3.
> Agree the initial part is emacs. But I suspect the confused bash
> business is not. ^G should either send SIGINT or not, this core dump
> thing is not cool.
Do you know whether this is Cygwin-specific? Have you checked to see
what happens on Linux?
Ken
--
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:[~2012-10-25 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 18:51 Ryan Johnson
2012-10-01 19:08 ` Ken Brown
2012-10-01 20:09 ` Ryan Johnson
2012-10-24 13:09 ` Ryan Johnson
2012-10-24 21:01 ` Ken Brown
2012-10-24 21:26 ` Ryan Johnson
2012-10-25 14:40 ` Ken Brown [this message]
2012-10-25 14:55 ` Ryan Johnson
2012-10-25 15:01 ` Eric Blake
2012-10-25 15:06 ` Ryan Johnson
2012-10-25 16:55 ` Eli Zaretskii
2012-10-25 17:06 ` ping
2012-10-25 20:08 ` Larry Hall (Cygwin)
2012-10-25 20:32 ` Ryan Johnson
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=50894F58.6050000@cornell.edu \
--to=kbrown@cornell.edu \
--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).