From: Eli Zaretskii <eliz@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 35204@debbugs.gnu.org
Subject: bug#35204: 27.0.50; Crash on Cygwin
Date: Tue, 09 Apr 2019 12:47:52 +0300 [thread overview]
Message-ID: <83ftqr7bnb.fsf@gnu.org> (raw)
In-Reply-To: <b4m4l77wqht.fsf@jpl.org> (message from Katsumi Yamaoka on Tue, 09 Apr 2019 17:07:58 +0900)
> Date: Tue, 09 Apr 2019 17:07:58 +0900
> From: Katsumi Yamaoka <yamaoka@jpl.org>
>
> 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 ?? ()
Is this when you run Emacs from GDB to begin with? If not, please run
Emacs from GDB, then the backtrace should be more informative.
> 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?)
How many threads are in the process? Did you type "bt" when the Lisp
thread was the current one?
> 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.
Did you build Emacs with -g3 switch to GCC?
next prev parent reply other threads:[~2019-04-09 9:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 8:07 bug#35204: 27.0.50; Crash on Cygwin Katsumi Yamaoka
2019-04-09 9:47 ` Eli Zaretskii [this message]
2019-04-10 4:54 ` Katsumi Yamaoka
2019-04-10 14:37 ` Eli Zaretskii
2019-04-11 2:31 ` Katsumi Yamaoka
2019-04-11 13:19 ` Eli Zaretskii
2019-04-11 23:02 ` Katsumi Yamaoka
2019-04-12 1:01 ` Katsumi Yamaoka
2019-04-12 7:11 ` Eli Zaretskii
2019-04-12 8:00 ` Katsumi Yamaoka
2019-04-12 14:54 ` Ken Brown
2019-04-12 15:15 ` Eli Zaretskii
2019-04-13 22:26 ` Basil L. Contovounesios
2019-04-13 22:50 ` Alex Gramiak
2019-04-14 2:15 ` Ken Brown
2019-04-14 23:26 ` Katsumi Yamaoka
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ftqr7bnb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35204@debbugs.gnu.org \
--cc=yamaoka@jpl.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).