GNU bug report logs -
#35204
27.0.50; Crash on Cygwin
Previous Next
Reported by: Katsumi Yamaoka <yamaoka <at> jpl.org>
Date: Tue, 9 Apr 2019 08:09:02 UTC
Severity: normal
Merged with 35259
Found in version 27.0.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
[Message part 1 (text/plain, inline)]
Your message dated Mon, 15 Apr 2019 08:26:15 +0900
with message-id <b4mh8b0i2y0.fsf <at> jpl.org>
and subject line Re: bug#35204: 27.0.50; Crash on Cygwin
has caused the debbugs.gnu.org bug report #35204,
regarding 27.0.50; Crash on Cygwin
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
35204: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35204
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Hi,
Recently Emacs on Cygwin suddenly crashes while it is (probably)
in idle, only it lives for several minuits, but reverting the
following three changes seems to help.
1. commit 0b8117ed1abfc17bb0bc1690a8997736f1e8f98c
; * src/frame.h (MonitorInfo): Remove const modifier
2. commit 7b78857c0ba69eafd780484641b858ae8a167044
; * src/xfns.c (x-display-monitor-attributes-list) Fix typo.
3. commit a35e06bbe27c5907f56c5aeb48182d7be00d1dec
Plug memory leak in GTK x-display-monitor-attributes-list
* src/frame.c (free_monitors) [USE_GTK]: Define in the GTK case as
well.
* src/xfns.c (x-display-monitor-attributes-list) [USE_GTK]: Plug
memory leak.
* src/frame.h (MonitorInfo): Declare name as pointing to const char.
I'm not sure what to do but please tell me anything I should do.
In GNU Emacs 27.0.50 (build 3, x86_64-pc-cygwin, GTK+ Version 3.22.28)
of 2019-04-09 built on localhost
Windowing system distributor 'The Cygwin/X Project', version 11.0.12004000
Configured using:
'configure CFLAGS=-O0 --verbose --with-x-toolkit=gtk3'
uname -a
CYGWIN_NT-10.0 localhost 3.0.6(0.338/5/3) 2019-04-06 16:18 x86_64 Cygwin
Here is a gdb backtrace I got after reverting only 1.:
(gdb) bt
#0 0x000000010054a66a in terminate_due_to_signal ()
#1 0x000000010057110d in handle_fatal_signal ()
#2 0x00000001005710e0 in deliver_thread_signal ()
#3 0x0000000100571149 in deliver_fatal_thread_signal ()
#4 0x0000000100571361 in handle_sigsegv ()
#5 0x000000018005f65a in altstack_wrapper (sig=<optimized out>,
siginfo=<optimized out>, sigctx=0xffffde50,
handler=0x1005712a5 <handle_sigsegv>)
at /usr/src/debug/cygwin-3.0.6-1/winsup/cygwin/exceptions.cc:1595
#6 0x0000000180062dfa in _cygtls::call_signal_handler (this=0xffffce00)
at /usr/src/debug/cygwin-3.0.6-1/winsup/cygwin/exceptions.cc:1777
#7 0x0000000000000000 in ?? ()
I couldn't fetch a backtrace for Emacs before reverting because
of an error:
(gdb) bt
#0 0x000000010054a72f in terminate_due_to_signal ()
#1 0x000303e90000faf0 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Couldn't fetch xbacktrace either:
(gdb) source .gdbinit
SIGINT is used by the debugger.
Are you sure you want to change it? (y or n) [answered Y; input not from terminal]
DISPLAY = :0.0
TERM = xterm
Breakpoint 1 at 0x10054a66a
.gdbinit:1228: Error in sourced command file:
No symbol "defined_HAVE_X_WINDOWS" in current context.
Thanks.
Regards,
[Message part 3 (message/rfc822, inline)]
On Sun, 14 Apr 2019 02:15:00 +0000, Ken Brown wrote:
>> It should be fixed with commit 7308c2edf, so please test again. Sorry
>> for the inconvenience.
> Yes, that fixes it for me.
Emacs built from the fresh git master works fine. Thanks a lot!
This bug report was last modified 6 years and 40 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.