From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.bugs Subject: bug#32258: 27.0.50; Crash on minimizing/maximizing Emacs frame from taskbar [RHEL 6.8 GTK2] Date: Tue, 24 Jul 2018 15:04:56 -0400 Message-ID: References: <83va94vgsy.fsf@gnu.org> <83pnzcv6pe.fsf@gnu.org> <83muugv4z8.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000bee4a60571c37002" X-Trace: blaine.gmane.org 1532459052 17400 195.159.176.226 (24 Jul 2018 19:04:12 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 24 Jul 2018 19:04:12 +0000 (UTC) Cc: 32258@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Jul 24 21:04:08 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fi2bP-0004P7-0S for geb-bug-gnu-emacs@m.gmane.org; Tue, 24 Jul 2018 21:04:07 +0200 Original-Received: from localhost ([::1]:42216 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fi2dV-0001cw-Fi for geb-bug-gnu-emacs@m.gmane.org; Tue, 24 Jul 2018 15:06:17 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36922) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fi2dL-0001cb-QX for bug-gnu-emacs@gnu.org; Tue, 24 Jul 2018 15:06:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fi2dH-0006Qe-No for bug-gnu-emacs@gnu.org; Tue, 24 Jul 2018 15:06:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:50783) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fi2dH-0006QW-Jt for bug-gnu-emacs@gnu.org; Tue, 24 Jul 2018 15:06:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fi2dG-0005wE-Dx for bug-gnu-emacs@gnu.org; Tue, 24 Jul 2018 15:06:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Kaushal Modi Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 24 Jul 2018 19:06:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32258 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 32258-submit@debbugs.gnu.org id=B32258.153245911822774 (code B ref 32258); Tue, 24 Jul 2018 19:06:02 +0000 Original-Received: (at 32258) by debbugs.gnu.org; 24 Jul 2018 19:05:18 +0000 Original-Received: from localhost ([127.0.0.1]:55801 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fi2cY-0005vG-A7 for submit@debbugs.gnu.org; Tue, 24 Jul 2018 15:05:18 -0400 Original-Received: from mail-lj1-f178.google.com ([209.85.208.178]:45055) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fi2cT-0005v1-R3 for 32258@debbugs.gnu.org; Tue, 24 Jul 2018 15:05:14 -0400 Original-Received: by mail-lj1-f178.google.com with SMTP id q127-v6so4522491ljq.11 for <32258@debbugs.gnu.org>; Tue, 24 Jul 2018 12:05:13 -0700 (PDT) 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=MxiTMIqwPyoxEEW6Jb5QzSly4Qw2DKtJp7WNn/oN2C4=; b=a55u+QgDBVV4nd+zbHMvc3jpaZECpKEedMZky+qyTCTKXS2KrX9muUdjg7ZZogaKj7 hO6RmLJCt7Xf3yOHBeZqn/v0cAQc7xqs0Tgg1yADaN0EVCrSMhtc457Kg+0X9J3PlDwW 24X7dpq+vh2XxDaN0y9H81dPOlipcSks2FErBMzfOzTaM9TuhtIOMmuajVfiYb5LxcXB LgQxtHqmD6y/IrbAjdC1bKJ4MTWgtmY0ivZNKjyLNo/zLGYkbL13Cjue3BcNBWtm0WPA KOdUATfIQkxc3c+oPss/Xdji4L6WU5hRq7mB1NpcQD0/nH7oj/g6QjuFRdabq2bwkOSw UtfA== 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=MxiTMIqwPyoxEEW6Jb5QzSly4Qw2DKtJp7WNn/oN2C4=; b=AV30ciQEJE10S4g6n6Ka4YhiRckmZufs97w6+A/2PYBUz9pxM32/IZg7O82xWHSPPX TTgb4AnVESnS5v53XrUyE4XF114Ojiix/iVGIzNxqg9Df4kjHIdbajXMdcD3c0Bvjujb 52dqKgjp1U5n5x8Nvpi7RgSaR0475cCX034c3eLDMAS9HcXyqPK8q5gJotpm3KPYpKM8 mIFfxbP0r5v2naNfyyQtxC3KTe3FzN+lgrpUyV+RfkoPN+l7VYPwb4vHViUzDkSzqQSA 835qsgQ8KiwpK7E0O8i5+v/KrQKE6ZG034SQkwH//0vDd7FRw4Xt3aLXBbITMU+6Vmo+ KGuA== X-Gm-Message-State: AOUpUlEpAPs+R0NWqC8Bgeo/HLYDnH+/1SN9QAi/CyZRnZq+PNkjHNsB aalETzyk+4TBJRaGDe/pdZlK9M/Mqy7rthpyGj0= X-Google-Smtp-Source: AAOMgpegn/A9QJJSi8oNzGVJH3qNusjBcvwiBGbyB0OOjW8X2T58BZLowCUOGZ/GxsC+lMDIiGMV92QN42xXs3ZfMiI= X-Received: by 2002:a2e:1c6:: with SMTP id f67-v6mr12594428lji.88.1532459107671; Tue, 24 Jul 2018 12:05:07 -0700 (PDT) In-Reply-To: <83muugv4z8.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: 208.118.235.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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:148901 Archived-At: --000000000000bee4a60571c37002 Content-Type: text/plain; charset="UTF-8" On Tue, Jul 24, 2018 at 2:55 PM Eli Zaretskii wrote: > > Then start Emacs via emacsclient as you usually do, and then > immediately attach GDB to it with "gdb -p PID" where PID is the > process ID of the Emacs process (NOT the emacsclient process!). Thanks. I was able to link gdb to the emacs process (Though, the only process containing "emacs" string was "emacs --daemon". I believe emacsclient launches that? I did not find a separate emacsclient process.) > When GDB shows its prompt "(gdb)", type "continue RET" to let Emacs > continue to run. Then do whatever you did before to cause the abort, > and GDB should kick in when you succeed. > I tried minimizing/maximizing the emacs frame quite a few times, but still no luck making it crash. Very strange. I think you can stop actively tracking this issue. I will update the issue when that crash happens again, or just close this bug if no crash happens in about a week :(. -- Kaushal Modi --000000000000bee4a60571c37002 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Jul 24= , 2018 at 2:55 PM Eli Zaretskii <eliz@gn= u.org> wrote:

Then start Emacs via emacsclient as you usually do, and then
immediately attach GDB to it with "gdb -p PID" where PID is the process ID of the Emacs process (NOT the emacsclient process!).

Thanks. I was able to link gdb to the emacs process (T= hough, the only process containing "emacs" string was "emacs= --daemon". I believe emacsclient launches that? I did not find a sepa= rate emacsclient process.)
=C2=A0
When GDB shows its prompt "(gdb)", type "continue R= ET" to let Emacs
continue to run.=C2=A0 Then do whatever you did before to cause the abort,<= br> and GDB should kick in when you succeed.

I tried minimizing/maximizing the emacs frame quite a few times, but stil= l no luck making it crash. Very strange.

I think you can stop actively trac= king this issue. I will update the issue when that crash happens again, or = just close this bug if no crash happens in about a week :(.
= --

Kaushal Modi

--000000000000bee4a60571c37002--