From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: 32258@debbugs.gnu.org
Subject: bug#32258: 27.0.50; Crash on minimizing/maximizing Emacs frame from taskbar [RHEL 6.8 GTK2]
Date: Tue, 24 Jul 2018 22:13:00 +0300 [thread overview]
Message-ID: <83k1pkv45f.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY2=kTQU_sD7cpc0_8VtasHtR2fgr3xHgZ2igLLW7dk7sg@mail.gmail.com> (message from Kaushal Modi on Tue, 24 Jul 2018 15:04:56 -0400)
> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Tue, 24 Jul 2018 15:04:56 -0400
> Cc: 32258@debbugs.gnu.org
>
> 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?
Yes.
> I tried minimizing/maximizing the emacs frame quite a few times, but still no luck making it crash. Very
> strange.
It probably means it's a Heisenbug: it's triggered by some specific
memory layout, and that changes under the debugger.
Are you still able to trigger the abort when running not under GDB?
If that's gone as well, try rebuilding Emacs by touching src/config.h
or somesuch, then try again.
next prev parent reply other threads:[~2018-07-24 19:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 12:06 bug#32258: 27.0.50; Crash on minimizing/maximizing Emacs frame from taskbar [RHEL 6.8 GTK2] Kaushal Modi
2018-07-24 13:36 ` Kaushal Modi
2018-07-24 13:52 ` Noam Postavsky
2018-07-24 13:59 ` Kaushal Modi
2018-07-24 14:39 ` Eli Zaretskii
2018-07-24 15:55 ` Kaushal Modi
2018-07-24 18:17 ` Eli Zaretskii
2018-07-24 18:26 ` Kaushal Modi
2018-07-24 18:55 ` Eli Zaretskii
2018-07-24 19:04 ` Kaushal Modi
2018-07-24 19:13 ` Eli Zaretskii [this message]
2018-07-24 19:35 ` Kaushal Modi
2018-07-26 13:42 ` Kaushal Modi
2018-07-26 17:59 ` Eli Zaretskii
2018-07-26 18:07 ` Kaushal Modi
2018-07-26 19:20 ` Eli Zaretskii
2018-07-26 20:13 ` Eli Zaretskii
2018-07-26 20:46 ` Kaushal Modi
2018-08-01 19:21 ` Kaushal Modi
2018-08-02 14:00 ` Eli Zaretskii
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=83k1pkv45f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32258@debbugs.gnu.org \
--cc=kaushal.modi@gmail.com \
/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.