From: Vladimir Nikishkin <lockywolf@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39081@debbugs.gnu.org
Subject: bug#39081: 26.3; Emacs hangs if external SCIM input method is killed
Date: Mon, 13 Jan 2020 08:03:27 +0800 [thread overview]
Message-ID: <CA+A2iZa_9dAvL8TCAmnoJxWyz09zmrbbMLrjju-Rcf_pOyp02A@mail.gmail.com> (raw)
In-Reply-To: <83h8107lwa.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
It's not really predictable. I didn't manage to reproduce the crash under
gdb so far, although without gdb it sometimes crashes and sometimes hands
under similar conditions. I'll keep running Emacs under gdb and if a crash
occurs, will post it here.
Eli Zaretskii <eliz@gnu.org> 於 2020年1月12日 週日 23:08 寫道：
> > From: Vladimir Nikishkin <lockywolf@gmail.com>
> > Date: Sun, 12 Jan 2020 14:49:12 +0800
> > Cc: 39081@debbugs.gnu.org
> >
> > Sorry, my debugging skills are too poor.
> >
> > So I attached gdb to Emacs, cont'd, then killed scim, and then
> > interrupted Emacs by issuing C-c in the gdb prompt,
> > and then collected a stack trace. I am not sure I am doing something
> > meaningful, as this is the first time I use gdb:
> > Here's the stack trace:
>
> Previously, you said that this unoptimized build "crashed, printing
> This is GTK bug". But I don't seed any crash here, just interrupted
> Emacs because you typed C-c. Does this mean you cannot reproduce the
> crash under GDB?
>
[-- Attachment #2: Type: text/html, Size: 1542 bytes --]
next prev parent reply other threads:[~2020-01-13 0:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 5:52 bug#39081: 26.3; Emacs hangs if external SCIM input method is killed Vladimir Nikishkin
2020-01-11 8:03 ` Eli Zaretskii
2020-01-11 8:29 ` Vladimir Nikishkin
2020-01-11 10:05 ` Eli Zaretskii
2020-01-12 6:05 ` Vladimir Nikishkin
2020-01-12 6:34 ` Eli Zaretskii
2020-01-12 6:40 ` Vladimir Nikishkin
2020-01-12 6:49 ` Vladimir Nikishkin
2020-01-12 15:08 ` Eli Zaretskii
2020-01-13 0:03 ` Vladimir Nikishkin [this message]
2020-01-14 3:54 ` Vladimir Nikishkin
2020-01-14 15:53 ` Eli Zaretskii
2020-01-14 16:24 ` Vladimir Nikishkin
2020-12-10 9:45 ` Vladimir Nikishkin
2020-12-10 10:29 ` Stefan Kangas
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=CA+A2iZa_9dAvL8TCAmnoJxWyz09zmrbbMLrjju-Rcf_pOyp02A@mail.gmail.com \
--to=lockywolf@gmail.com \
--cc=39081@debbugs.gnu.org \
--cc=eliz@gnu.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).