GNU bug report logs - #32258
27.0.50; Crash on minimizing/maximizing Emacs frame from taskbar [RHEL 6.8 GTK2]

Previous Next

Full log

Message #32 received at 32258 <at> debbugs.gnu.org (full text, mbox):

From: Kaushal Modi <kaushal.modi <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 32258 <at> debbugs.gnu.org
Subject: Re: 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 part 1 (text/plain, inline)]

On Tue, Jul 24, 2018 at 2:55 PM Eli Zaretskii <eliz <at> gnu.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 (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

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.