From: Eli Zaretskii <eliz@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>, Ken Brown <kbrown@cornell.edu>
Cc: 35204@debbugs.gnu.org
Subject: bug#35204: 27.0.50; Crash on Cygwin
Date: Fri, 12 Apr 2019 10:11:12 +0300 [thread overview]
Message-ID: <83a7gv4s1b.fsf@gnu.org> (raw)
In-Reply-To: <b4mzhow2liu.fsf@jpl.org> (message from Katsumi Yamaoka on Fri, 12 Apr 2019 08:02:33 +0900)
> Date: Fri, 12 Apr 2019 08:02:33 +0900
> From: Katsumi Yamaoka <yamaoka@jpl.org>
> Cc: 35204@debbugs.gnu.org
>
> > (gdb) thread 1
> > (gdb) bt
>
> The result is in the first attachment, and
>
> > And please separately do also this:
>
> > (gdb) info threads
>
> that of it is in the second attachment.
>
> > and post the results.
It's strange. Looks like there's a bug in your GDB, because it dumps
core in this case. I also don't understand why the backtrace ends in
the exception handler, it sounds like GDB is not given the first
opportunity to handle an exception, as it should? Maybe try upgrading
to GDB 8.2, if its Cygwin port is available?
Ken, could you please chime in? It is strange that this problem only
affects the Cygwin build, and no other bug report points to that
change from other GTK builds, including not from other Cygwin users.
So it sounds like a Cygwin problem, perhaps triggered by something on
Yamaoka-san's machine, but the fact that GDB crashes doesn't allow any
reasonable way of investigating the problem past the exception
handler. I don't know what to do next.
next prev parent reply other threads:[~2019-04-12 7:11 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a7gv4s1b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35204@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.