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 11:55:54 -0400 Message-ID: References: <83va94vgsy.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000c00f860571c0cc15" X-Trace: blaine.gmane.org 1532447709 31601 195.159.176.226 (24 Jul 2018 15:55:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 24 Jul 2018 15:55:09 +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 17:55:05 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 1fhzeS-00086n-Pg for geb-bug-gnu-emacs@m.gmane.org; Tue, 24 Jul 2018 17:55:05 +0200 Original-Received: from localhost ([::1]:41236 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fhzgZ-0008Nq-He for geb-bug-gnu-emacs@m.gmane.org; Tue, 24 Jul 2018 11:57:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60449) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fhzgR-0008MI-LY for bug-gnu-emacs@gnu.org; Tue, 24 Jul 2018 11:57:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fhzgM-0008Mv-P7 for bug-gnu-emacs@gnu.org; Tue, 24 Jul 2018 11:57:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:50677) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fhzgM-0008Mj-Ks for bug-gnu-emacs@gnu.org; Tue, 24 Jul 2018 11:57:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fhzgM-0001Ly-85 for bug-gnu-emacs@gnu.org; Tue, 24 Jul 2018 11:57:02 -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 15:57: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.15324477755142 (code B ref 32258); Tue, 24 Jul 2018 15:57:02 +0000 Original-Received: (at 32258) by debbugs.gnu.org; 24 Jul 2018 15:56:15 +0000 Original-Received: from localhost ([127.0.0.1]:55695 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fhzfb-0001Ks-1X for submit@debbugs.gnu.org; Tue, 24 Jul 2018 11:56:15 -0400 Original-Received: from mail-lj1-f169.google.com ([209.85.208.169]:43715) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fhzfY-0001Ke-ON for 32258@debbugs.gnu.org; Tue, 24 Jul 2018 11:56:13 -0400 Original-Received: by mail-lj1-f169.google.com with SMTP id r13-v6so4045884ljg.10 for <32258@debbugs.gnu.org>; Tue, 24 Jul 2018 08:56:12 -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=+yYdy1wBbWhzYyKfbQTzoAEBQ9qbTLzTb7bb/WZHBJQ=; b=HSDUDE8mfeYatJOX+nlGVwCUrDgvGIzvOZ9jmza5HEtxnK6L7Fn6DGUAq0qhxNLGCx mQ07KN08Nw3TIFlcfHSGX79VcgGl/oi7uBJboCM0IZD5x1rLJvozVfBpzpzIIyn2jvS0 Hv6JRex1b2vCNxwIS79dGK6h9dCD+o15b6Lanb+xUpCX1/mBMLl86aECiiS2yuNhOW76 +DS97bAY6KC8CNy0Wo0ACJWrXHvVzBP5P36vre4w6cRuLwYLl1e0gW1/MnZDkrXa8w32 GRE+XaJhq51GOV5nxlnxF3AdPoY+3vRP+Xb+0ddX0AC4ufpqq12V4Cg5nXsFkzwfpMhh JqyQ== 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=+yYdy1wBbWhzYyKfbQTzoAEBQ9qbTLzTb7bb/WZHBJQ=; b=LtLIqzetY97zHrHyFtQlAw5x2IqAAVtPw1yVf7yFF1MNpIG5ZgIcRdHZuLnoJmkWnm TlwnCn56IYSBIi/p3GCStqGq+mre0m0RXvSbCjkI+m3Aginj+TbSvqmv0tZi5IOZIwsd /lZY8OuUHgw4ggvQMkrZ8YqrZdEOBgWs1CR2beiziuiXCdpm9QEEXvFlU6S9VBnvu5w2 YeQYQXVKp5r7BRPKRCxtJSwcg2Reu/h8gMKjHoPFijABV2dqlsL2BrJbOA9AvCXtvtbd 7aUJqoZvj2SxrxP11eL1NEj4+HdI8AptzDhfaXpchn/m1bsZc91AC18FfzZrPQ69H+hh 7t1g== X-Gm-Message-State: AOUpUlFTl5X+fSJlRyFKwW2LUYJqV/IcZfgTfSzudPOz6cOFgLbGcrGN 2WYJK5I+2P6wvcC6FL2109tem4PJ3I/1f7K1ULCEp6Gx X-Google-Smtp-Source: AAOMgpeVA5NCyQc7qsubLzmOLYzNCmcG7+t/4bUO8VcTyX5F5NN3ouQwaFT0fGMrHR+lWD63rN+DklDz131OiFTve7g= X-Received: by 2002:a2e:1c6:: with SMTP id f67-v6mr12187080lji.88.1532447766350; Tue, 24 Jul 2018 08:56:06 -0700 (PDT) In-Reply-To: <83va94vgsy.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:148892 Archived-At: --000000000000c00f860571c0cc15 Content-Type: text/plain; charset="UTF-8" Hello Eli, On Tue, Jul 24, 2018 at 10:39 AM Eli Zaretskii wrote: > > You don't need to set breakpoints when you know Emacs will crash (or > abort due to an assertion violation, which has the same effect). Just > run Emacs, and when the assertion violation happens, GDB will kick in > automatically, and you will be able to display the C backtrace, look > at related variables, etc. > Thanks. I did not know that. I was just living by my notes. The only time I use gdb is to report Emacs bugs. But now that I have emacs running through gdb, I am failing to get that crash.. and without that, I got that crash 4 times since yesterday (and 2-3 times in the past week). I use emacsclient by default. But in gdb I run ./emacs. Based on the assertion failure in: ,-------- #21236 -- /home/kmodi/downloads/git/emacs/src/xdisp.c --- | eassert (it->glyph_row == NULL || it->glyph_row->used[TEXT_AREA] == 0); `-------- #21236 -- 2018/07/24 -- kmodi would that make any difference? If yes, how do I run emacsclient from gdb? -- Kaushal Modi --000000000000c00f860571c0cc15 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Eli,

On Tue, Jul 24, 2018 at 10:39 AM Eli Zaretskii &= lt;eliz@gnu.org> wrote:

You don't need to set breakpoints when you know Emacs will crash (or abort due to an assertion violation, which has the same effect).=C2=A0 Just=
run Emacs, and when the assertion violation happens, GDB will kick in
automatically, and you will be able to display the C backtrace, look
at related variables, etc.

Thanks. I di= d not know that. I was just living by my notes. The only time I use gdb is = to report Emacs bugs.

But now that I have emacs r= unning through gdb, I am failing to get that crash.. and without that, I go= t that crash 4 times since yesterday (and 2-3 times in the past week).

I use emacsclient by default. But in gdb I run ./emacs= . Based on the assertion failure in:

,-------- #21= 236 -- /home/kmodi/downloads/git/emacs/src/xdisp.c ---
| eassert (it->= ;glyph_row =3D=3D NULL || it->glyph_row->used[TEXT_AREA] =3D=3D 0);`-------- #21236 -- 2018/07/24 -- kmodi

would th= at make any difference?

If yes, how do I run emacs= client from gdb?
--

Kaus= hal Modi

--000000000000c00f860571c0cc15--