From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Vladimir Nikishkin Newsgroups: gmane.emacs.bugs Subject: bug#39081: 26.3; Emacs hangs if external SCIM input method is killed Date: Mon, 13 Jan 2020 08:03:27 +0800 Message-ID: References: <87lfqey1xj.fsf@delllaptop.lockywolf.net> <83blra8lnb.fsf@gnu.org> <83wo9y71gt.fsf@gnu.org> <83h8107lwa.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000043070c059bfa3925" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="111627"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 39081@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 13 01:05:19 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iqnEH-000PLz-Cd for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 13 Jan 2020 01:05:13 +0100 Original-Received: from localhost ([::1]:43074 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iqnEF-0007iC-H9 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 12 Jan 2020 19:05:11 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35595) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iqnE7-0007i5-Ho for bug-gnu-emacs@gnu.org; Sun, 12 Jan 2020 19:05:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iqnE6-00078c-Ed for bug-gnu-emacs@gnu.org; Sun, 12 Jan 2020 19:05:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:52479) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iqnE6-00078M-Bo for bug-gnu-emacs@gnu.org; Sun, 12 Jan 2020 19:05:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iqnE6-0004Wx-72 for bug-gnu-emacs@gnu.org; Sun, 12 Jan 2020 19:05:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Vladimir Nikishkin Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 13 Jan 2020 00:05:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 39081 X-GNU-PR-Package: emacs Original-Received: via spool by 39081-submit@debbugs.gnu.org id=B39081.157887389517394 (code B ref 39081); Mon, 13 Jan 2020 00:05:02 +0000 Original-Received: (at 39081) by debbugs.gnu.org; 13 Jan 2020 00:04:55 +0000 Original-Received: from localhost ([127.0.0.1]:58451 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iqnDz-0004WT-GA for submit@debbugs.gnu.org; Sun, 12 Jan 2020 19:04:55 -0500 Original-Received: from mail-ed1-f54.google.com ([209.85.208.54]:45640) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iqnDy-0004WF-CO for 39081@debbugs.gnu.org; Sun, 12 Jan 2020 19:04:54 -0500 Original-Received: by mail-ed1-f54.google.com with SMTP id v28so6923491edw.12 for <39081@debbugs.gnu.org>; Sun, 12 Jan 2020 16:04:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YMUo54I7IezXJ1GvEc4tdp0WPsfm4bBfmZ6RHSnmQ/E=; b=aRuM5Kzz6JGVeD2UhVrNpcggl/OrlNpQ/2hO5Wwa0A+JL1aQNMT0vCwBZBjrw8oDdh tR0Pth66o9/omMRvp4FgMwV/tlmemCic6uQetTeDUZV/er37U9rZWeGMxMnDPXf1C09O wULuVTQzRkQ+KFeKW1z8atIw+ZRDTrfjGY/HaQoQw+DvHWy86L4EmQJ+GTvSCiNtrH7L qX9XLpHROrJq7STz/I3IR1OIKj2PxAYzA096PXxIKmBBGUHJK6vRsDguypZ2BeD5oyEb /eU6vUfwX+c2wKpTOidHnCC94mAHLooQvj4UNwXXxGydSiMUsqQ5+O+l4yS7kkRkHsMs wIuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YMUo54I7IezXJ1GvEc4tdp0WPsfm4bBfmZ6RHSnmQ/E=; b=l0P7wGWnUcLemBJrm2g+gMkrvVAjuET6iY8ITPqURpzw3puEJI/Tpo1XPAhmxZx/TQ BEjy7Iu3FbeSyEJsSwlMuhULOC2YGcotUOBDeQzlw0m34Jg2ZjpxCClPAc3oOfQWaOEZ j3qGjAsO4UQD4PWJLQwa+40Fuv4CRixOxVA7n5OYBsXqXVGmBHh4ZtP3kqZ3KpgH3K0W IuuksY5FOFjDEjaIjrTZpFfj+a9VsOT7W6EojUsp0vKZuD84lEju1s/OfFsWPoV/N6sd +BjNfPPvuYDhh5DuCmf+ita0LYrUTIWWv1JUeJgHBfAsbih3GHeCFSXJRnIGJrWWsyiJ 0dAA== X-Gm-Message-State: APjAAAVkW7vghmRIIhp+KGb15dVyRNNQkRgnVxQgXvI0ZPjaR2wxM05L J018d92MZErj5bzJFBF5ad5TMyXTgHCFMozzouECiRQM X-Google-Smtp-Source: APXvYqz1bhgykKI6dlDXiMVxjUfzYWaj9yTGfjSFmk1O2yAan/tud+eP6hLO0+S92lsDlSUABphxp3BlVSbNxCOKGRE= X-Received: by 2002:a50:8d13:: with SMTP id s19mr14780659eds.40.1578873888373; Sun, 12 Jan 2020 16:04:48 -0800 (PST) In-Reply-To: <83h8107lwa.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:174519 Archived-At: --00000000000043070c059bfa3925 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 =E6=96=BC 2020=E5=B9=B41=E6=9C=8812=E6=97=A5 = =E9=80=B1=E6=97=A5 23:08 =E5=AF=AB=E9=81=93=EF=BC=9A > > From: Vladimir Nikishkin > > 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? > --00000000000043070c059bfa3925 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
It's not really predictable. I didn't manage to r= eproduce the crash under gdb so far, although without gdb it sometimes cras= hes and sometimes hands under similar conditions. I'll keep running Ema= cs under gdb and if a crash occurs, will post it here.

Eli Zaretskii <eliz@gnu.org> =E6=96=BC 2020=E5=B9=B41= =E6=9C=8812=E6=97=A5 =E9=80=B1=E6=97=A5 23:08 =E5=AF=AB=E9=81=93=EF=BC=9A
> From: Vladimir Nikishkin <l= ockywolf@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".=C2=A0 But I don't seed any crash here, just inte= rrupted
Emacs because you typed C-c.=C2=A0 Does this mean you cannot reproduce the<= br> crash under GDB?
--00000000000043070c059bfa3925--