GNU bug report logs - #15247
24.3.50; Emacs Cygwin crashes when replying to a mail

Previous Next

Package: emacs;

Reported by: Katsumi Yamaoka <yamaoka <at> jpl.org>

Date: Mon, 2 Sep 2013 06:03:02 UTC

Severity: normal

Found in version 24.3.50

Done: Katsumi Yamaoka <yamaoka <at> jpl.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Katsumi Yamaoka <yamaoka <at> jpl.org>
Subject: bug#15247: closed (Re: bug#15247: 24.3.50; Emacs Cygwin crashes
 when replying to a mail)
Date: Mon, 02 Sep 2013 10:03:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#15247: 24.3.50; Emacs Cygwin crashes when replying to a mail

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 15247 <at> debbugs.gnu.org.

-- 
15247: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15247
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Katsumi Yamaoka <yamaoka <at> jpl.org>
To: 15247-done <at> debbugs.gnu.org
Subject: Re: bug#15247: 24.3.50; Emacs Cygwin crashes when replying to a mail
Date: Mon, 02 Sep 2013 19:02:37 +0900
Katsumi Yamaoka wrote:
> Recently Emacs on Cygwin crashes pretty often when I try to reply
> to a mail in a new frame[1] using Gnus.  I feel the frequency gets
> high if a mail cites Japanese and Chinese mixture text (so, it's
> due to decoding of characters?).  But it hardly crashes if I have
> a new empty message frame in advance besides the summary frame.

I realized that this is caused by `make-frame-invisible' that runs
when there is only one Emacs frame.  At least for Cygwin, you should
be able to reproduce it in this way:

emacs -Q --eval '(make-frame-invisible (selected-frame) t)'

I also guess that it was harmless until about a week ago.

Why such an odd thing was run is because I was using this advice
to make `raise-frame' work on Cygwin.

(defadvice raise-frame (before make-it-work (&optional frame) activate)
  "Make it work on Cygwin."
  (make-frame-invisible frame t))

As I wrote in <http://thread.gmane.org/gmane.emacs.devel/150533>,
`raise-frame' doesn't raise iconified, invisible, or hidden frame.
Now I changed it into:

(defadvice raise-frame (before make-it-work (&optional frame) activate)
  "Make it work on Cygwin."
  (or (eq frame (selected-frame))
      (make-frame-invisible frame)))

Even if Emacs should not crash for any Lisp code, it's a trivial
one among many(?) issues concerning Cygwin.  So, I'm closing this
bug.  Sorry for the noise.

[Message part 3 (message/rfc822, inline)]
From: Katsumi Yamaoka <yamaoka <at> jpl.org>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.3.50; Emacs Cygwin crashes when replying to a mail
Date: Mon, 02 Sep 2013 15:02:16 +0900
Hi,

Recently Emacs on Cygwin crashes pretty often when I try to reply
to a mail in a new frame[1] using Gnus.  I feel the frequency gets
high if a mail cites Japanese and Chinese mixture text (so, it's
due to decoding of characters?).  But it hardly crashes if I have
a new empty message frame in advance besides the summary frame.
It happened too also when I used the LUCID toolkit last week.
I don't know what's wrong, sorry, but a gdb backtrace is attached.

Thanks.

[1] I use:
    http://www.jpl.org/ftp/pub/elisp/message-multiple-frames.el.gz
    It pops up a message frame after composing it.

In GNU Emacs 24.3.50.1 (i686-pc-cygwin, GTK+ Version 3.8.2)
 of 2013-09-02 on localhost
Bzr revision: 114096 dmantipov <at> yandex.ru-20130902033906-qqu9pis0ksze2lmg
Windowing system distributor `The Cygwin/X Project', version 11.0.11402000
Configured using:
Configured using:
 `configure --verbose --with-x-toolkit=gtk3 --without-imagemagick
 --without-dbus --without-gconf --without-gsettings'

Important settings:
  value of $LC_CTYPE: ja_JP.UTF-8
  value of $LC_MESSAGES: C
  value of $LANG: C
  locale-coding-system: utf-8-unix
  default enable-multibyte-characters: t

A backtrace follows:

GNU gdb (GDB) 7.6.50.20130728-cvs (cygwin-special)
[...]
Fatal error 6: Aborted
Program received signal SIGABRT, Aborted.
terminate_due_to_signal (sig=2265648, backtrace_limit=164) at emacs.c:372
372       exit (1);
(gdb) bt
#0  terminate_due_to_signal (sig=2265648, backtrace_limit=164) at emacs.c:372
#1  0x3818cf46 in ?? ()
#2  0x00229230 in ?? ()
#3  0x7693543c in WriteFile () from /cygdrive/c/windows/system32/kernel32.dll
#4  0x610dc5a0 in sig_send(_pinfo*, siginfo_t&, _cygtls*)@12 (p=0x60fd0000,
    p <at> entry=0x0, si=..., tls=tls <at> entry=0x0)
    at /usr/src/debug/cygwin-1.7.24-1/winsup/cygwin/sigproc.cc:624
#5  0x610d9c4d in _pinfo::kill(siginfo_t&)@8 (this=0x0, si=...)
    at /usr/src/debug/cygwin-1.7.24-1/winsup/cygwin/signal.cc:248
#6  0x00229274 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)



This bug report was last modified 11 years and 268 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.