Emacs crashing on C-x C-g

Emacs crashing on C-x C-g

[Ryan Johnson]

Hi all,

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. I can't reproduce it reliably, but it's been awfully hard on my 
population of venerable emacs sessions, which used to go for weeks at a 
time between windows update reboots.

I'll keep an eye out for more hints on what's going on, but meanwhile, 
has anyone else had this happen to them?

cygwin-1.7.16-1
emacs-x11-24.2-1 [2][3]
mintty-1.1.2-1 [4]

Thanks,
Ryan

[1] Usually due to starting some C-x command and then changing my mind
[2] I always use it in terminal mode, because normal emacs is not 
mouse-aware
[3] I recently upgraded from emacs 24.1 to 24.2, and that cut the 
frequency quite a bit, but it still happens occasionally
[4] I recently upgraded from mintty 1.1.1, but that didn't seem to make 
a difference


--
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

Re: Emacs crashing on C-x C-g

[Ken Brown]

On 10/1/2012 2:51 PM, Ryan Johnson wrote:
> Hi all,
>
> 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. I can't reproduce it reliably, but it's been awfully hard on my
> population of venerable emacs sessions, which used to go for weeks at a
> time between windows update reboots.
>
> I'll keep an eye out for more hints on what's going on, but meanwhile,
> has anyone else had this happen to them?
>
> cygwin-1.7.16-1
> emacs-x11-24.2-1 [2][3]
> mintty-1.1.2-1 [4]

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).

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

Re: Emacs crashing on C-x C-g

[Ryan Johnson]

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.

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

Re: Emacs crashing on C-x C-g

[Ryan Johnson]

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.

Packages:
cygwin snapshot 1.7.17s(0.262/5/3) 20120917
bash-4.1.10-4
emacs-24.2-1
emacs-x11-24.2-1
mercurial-2.3.1-1
mintty-1.1.2-1

This time the crash is reproducible, and the test case below paints an 
"interesting" story:

mkdir foo
cd foo
hg init
touch foo
hg add foo
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!">>>
python
C-g
<<<"KeyboardInterrupt">>>
quit # python still running
reset -i ^c
<<<no message>>>
hg record foo
C-g
<<<"Quit (core dumped)">>>
hg record foo
C-c
<<<"interrupted">>>
python
C-g
<<<"Quit (core dumped)">>>
python
C-c
<<<"KeyboardInterrupt">>>
quit # python still running

Apparently, emacs sets the terminal's interrupt character to ^G, causing 
^G to interrupt the python script controlling emacs, causing the latter 
to not set interrupt back to ^C (due to abnormal exit), and causing 
serious (and permanent) confusion for bash: after setting the interrupt 
char back to ^C, ^C behaves as expected, but ^G crashes the app. In 
addition to mercurial/python above, the same core dump occurs with 
gnuplot, cat, and bash history search (^R). Hitting ^G during any of 
those commands in a fresh mintty has the usual harmless result.

The stackdump for python killed by a zombie ^G contains:

Stack trace:
Frame     Function  Args
# 767... => kernel32.dll
0028A49C  767F1A2C  (00000003, FFFDE000, 00000000, FFFFFFFF)
0028A4B8  767F4220  (00000003, 0028A4F0, 00000000, FFFFFFFF)
# 610... => cygwin1.dll
0028A608  610D17C8  (0028A6D8, 0028A670, 0028A650, 0028A630)
0028A738  610D1FBF  (0028A790, FFFFFFFF, 0000000C, 610FD52A)
0028A7D8  610D244F  (00000001, 0028A828, 00000000, 00000000)
0028A848  610D66C5  (611876B0, 61187720, FFF46034, 800D0000)
# 64B => libpython2.6.dll
0028A888  64B45128  (611876B0, 61187720, FFF46034, FFFFF000)
0028A8D8  64B45CB6  (0028A8A0, 61106469, 0053002B, 002B002B)
0028A998  64B46CD7  (800ACF40, 0028A9DC, 0028A9D8, 64B428F9)
0028A9F8  64B423A4  (0028AA3C, 0028AA58, 64C442C0, 00000100)
0028AA78  64C01327  (611876B0, 64C78A32, 00000100, FFF46034)
0028AAD8  64C02559  (611876B0, 64C78A32, 0028AC2C, 64C78A32)
0028AB28  64C02786  (611876B0, 64C78A32, 0028AC2C, 6102C349)
0028AB68  64C0424B  (611876B0, 64C78A32, 00000000, 0028AC2C)
0028AC48  64C11589  (00000001, 0028AC90, 00000000, 0028CE64)
# 004... => python2.6.exe
0028AC68  00401190  (00000001, 0028AC90, 80010100, 61275B98)
End of stack trace (more stack frames may be present)

Pulling down the .dbg for this snapshot and running the cygwin1.dll 
addresses though addr2line gives:
select_stuff::wait(_types_fd_set*, _types_fd_set*, _types_fd_set*, 
unsigned long) at select.cc:368
select at select.cc:190
cygwin_select at select.cc:125
?? at ??:0

Ideas?
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

Re: Emacs crashing on C-x C-g

[Ken Brown]

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.
>
> Packages:
> cygwin snapshot 1.7.17s(0.262/5/3) 20120917
> bash-4.1.10-4
> emacs-24.2-1
> emacs-x11-24.2-1
> mercurial-2.3.1-1
> mintty-1.1.2-1
>
> This time the crash is reproducible, and the test case below paints an
> "interesting" story:
>
> mkdir foo
> cd foo
> hg init
> touch foo
> hg add foo
> 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!">>>
> python
> C-g
> <<<"KeyboardInterrupt">>>
> quit # python still running
> reset -i ^c
> <<<no message>>>
> hg record foo
> C-g
> <<<"Quit (core dumped)">>>
> hg record foo
> C-c
> <<<"interrupted">>>
> python
> C-g
> <<<"Quit (core dumped)">>>
> python
> C-c
> <<<"KeyboardInterrupt">>>
> quit # python still running
>
> Apparently, emacs sets the terminal's interrupt character to ^G, causing
> ^G to interrupt the python script controlling emacs, causing the latter
> to not set interrupt back to ^C (due to abnormal exit), and causing
> serious (and permanent) confusion for bash: after setting the interrupt
> char back to ^C, ^C behaves as expected, but ^G crashes the app. In
> addition to mercurial/python above, the same core dump occurs with
> gnuplot, cat, and bash history search (^R).

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.

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

Re: Emacs crashing on C-x C-g

[Ryan Johnson]

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.

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

Re: Emacs crashing on C-x C-g

[Ken Brown]

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

Re: Emacs crashing on C-x C-g

[Ryan Johnson]

On 25/10/2012 10:40 AM, Ken Brown wrote:
> 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?
Oops, you're right: I see the exact same behavior on linux. However, 
that's via ssh in a mintty window, so it could still be mintty. Can 
somebody running Linux directly verify, perhaps?

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

Re: Emacs crashing on C-x C-g

[Eric Blake]

[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]

On 10/25/2012 08:55 AM, Ryan Johnson wrote:
>>>>
>>>>   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?
> Oops, you're right: I see the exact same behavior on linux. However,
> that's via ssh in a mintty window, so it could still be mintty. Can
> somebody running Linux directly verify, perhaps?

Linux (at least my setup on Fedora 17) has the same problem - when using
emacs as the editor under 'git commit', an ill-timed ctrl-G on my part
unceremoniously kills emacs as a result of sending the SIGINT to the
entire process group.  I hate the behavior, but it is definitely not
cygwin-specific.

-- 
Eric Blake   eblake@redhat.com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 617 bytes --]

Re: Emacs crashing on C-x C-g

[Ryan Johnson]

On 25/10/2012 11:01 AM, Eric Blake wrote:
> On 10/25/2012 08:55 AM, Ryan Johnson wrote:
>>>>>    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?
>> Oops, you're right: I see the exact same behavior on linux. However,
>> that's via ssh in a mintty window, so it could still be mintty. Can
>> somebody running Linux directly verify, perhaps?
> Linux (at least my setup on Fedora 17) has the same problem - when using
> emacs as the editor under 'git commit', an ill-timed ctrl-G on my part
> unceremoniously kills emacs as a result of sending the SIGINT to the
> entire process group.  I hate the behavior, but it is definitely not
> cygwin-specific.
Right, but what happens to processes when you hit ^G after resetting the 
terminal to use ^C? Does it cause a seg fault? That's the part that 
might still be cygwin-specific.

And yes, hopefully emacs fixes this Real Soon Now...

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

Re: Emacs crashing on C-x C-g

[Eli Zaretskii]

> Date: Thu, 25 Oct 2012 09:01:40 -0600
> From: Eric Blake <eblake@redhat.com>
> 
> On 10/25/2012 08:55 AM, Ryan Johnson wrote:
> >>>>
> >>>>   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?
> > Oops, you're right: I see the exact same behavior on linux. However,
> > that's via ssh in a mintty window, so it could still be mintty. Can
> > somebody running Linux directly verify, perhaps?
> 
> Linux (at least my setup on Fedora 17) has the same problem - when using
> emacs as the editor under 'git commit', an ill-timed ctrl-G on my part
> unceremoniously kills emacs as a result of sending the SIGINT to the
> entire process group.  I hate the behavior, but it is definitely not
> cygwin-specific.

Why doesn't git block SIGINT when it invokes $EDITOR?  I think that's
the prudent thing to do.

--
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

Re: Emacs crashing on C-x C-g

[ping]

On 10/25/2012 12:54 PM, Eli Zaretskii wrote:
>> Date: Thu, 25 Oct 2012 09:01:40 -0600
>> From: Eric Blake <eblake@redhat.com>
>>
>> On 10/25/2012 08:55 AM, Ryan Johnson wrote:
>>>>>>    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?
>>> Oops, you're right: I see the exact same behavior on linux. However,
>>> that's via ssh in a mintty window, so it could still be mintty. Can
>>> somebody running Linux directly verify, perhaps?
>> Linux (at least my setup on Fedora 17) has the same problem - when using
>> emacs as the editor under 'git commit', an ill-timed ctrl-G on my part
>> unceremoniously kills emacs as a result of sending the SIGINT to the
>> entire process group.  I hate the behavior, but it is definitely not
>> cygwin-specific.
> Why doesn't git block SIGINT when it invokes $EDITOR?  I think that's
> the prudent thing to do.
>
> --
> 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
>
the simplest solution: change to vim.
I don't know of any extra benefit using emacs instead of vim...

--
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

Re: Emacs crashing on C-x C-g

[Larry Hall (Cygwin)]

On 10/25/2012 1:06 PM, ping wrote:
> On 10/25/2012 12:54 PM, Eli Zaretskii wrote:
>>> Date: Thu, 25 Oct 2012 09:01:40 -0600
>>> From: Eric Blake <eblake@redhat.com>
>>>
>>> On 10/25/2012 08:55 AM, Ryan Johnson wrote:
>>>>>>>    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?
>>>> Oops, you're right: I see the exact same behavior on linux. However,
>>>> that's via ssh in a mintty window, so it could still be mintty. Can
>>>> somebody running Linux directly verify, perhaps?
>>> Linux (at least my setup on Fedora 17) has the same problem - when using
>>> emacs as the editor under 'git commit', an ill-timed ctrl-G on my part
>>> unceremoniously kills emacs as a result of sending the SIGINT to the
>>> entire process group.  I hate the behavior, but it is definitely not
>>> cygwin-specific.
>> Why doesn't git block SIGINT when it invokes $EDITOR?  I think that's
>> the prudent thing to do.
> the simplest solution: change to vim.
> I don't know of any extra benefit using emacs instead of vim...

It's been 3 hours and not a single flame.  Have the Editor Wars
actually died out?  Maybe there's hope for peace in the Middle East
too. ;-)

(Please interpret the above as an attempt at humor and not a plea
to restart debates on the best editor.)

--
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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

Re: Emacs crashing on C-x C-g

[Ryan Johnson]

On 25/10/2012 4:07 PM, Larry Hall (Cygwin) wrote:
> On 10/25/2012 1:06 PM, ping wrote:
>> On 10/25/2012 12:54 PM, Eli Zaretskii wrote:
>>>> Date: Thu, 25 Oct 2012 09:01:40 -0600
>>>> From: Eric Blake <eblake@redhat.com>
>>>>
>>>> On 10/25/2012 08:55 AM, Ryan Johnson wrote:
>>>>>>>> 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?
>>>>> Oops, you're right: I see the exact same behavior on linux. However,
>>>>> that's via ssh in a mintty window, so it could still be mintty. Can
>>>>> somebody running Linux directly verify, perhaps?
>>>> Linux (at least my setup on Fedora 17) has the same problem - when 
>>>> using
>>>> emacs as the editor under 'git commit', an ill-timed ctrl-G on my part
>>>> unceremoniously kills emacs as a result of sending the SIGINT to the
>>>> entire process group.  I hate the behavior, but it is definitely not
>>>> cygwin-specific.
>>> Why doesn't git block SIGINT when it invokes $EDITOR?  I think that's
>>> the prudent thing to do.
>> the simplest solution: change to vim.
>> I don't know of any extra benefit using emacs instead of vim...
>
> It's been 3 hours and not a single flame.  Have the Editor Wars
> actually died out?  Maybe there's hope for peace in the Middle East
> too. ;-)
At first I thought ping was suggesting to close all present and future 
vim bugs with "works for me, I use emacs."

But that would be completely absurd, so I concluded it must have been a 
joke.

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