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

Previous Next

Package: emacs;

Reported by: Kaushal Modi <kaushal.modi <at> gmail.com>

Date: Tue, 24 Jul 2018 12:07:02 UTC

Severity: normal

Found in version 27.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


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

From: Noam Postavsky <npostavs <at> gmail.com>
To: Kaushal Modi <kaushal.modi <at> gmail.com>
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 09:52:47 -0400
Kaushal Modi <kaushal.modi <at> gmail.com> writes:

> Thread 1 "emacs" hit Breakpoint 3, Fsignal (error_symbol=XIL(0xd980),
> data=XIL(0x127f163))
>     at eval.c:1582
> 1582      signal_or_quit (error_symbol, data, false);
> (gdb) r -Q
> The program being debugged has been started already.
> Start it from the beginning? (y or n) n
> Program not restarted.
> (gdb) p error_symbol
> $1 = XIL(0xd980)
> (gdb) xsymbol
> $2 = (struct Lisp_Symbol *) 0xe1b2c0 <lispsym+55680>
> "void-variable"
> (gdb) condition 3 error_symbol!=XIL(0xd980)
> (gdb) c
> Continuing.
> Error in testing breakpoint condition:
> Structure has no component named operator!=.
> Error in testing breakpoint condition:
> Structure has no component named operator!=.

This works for me:

    condition 3 !EQ (error_symbol, XIL(0xd980))

Using $1 instead of XIL(0xd980) also works (and in this case,
Qvoid_variable is an option too).




This bug report was last modified 6 years and 293 days ago.

Previous Next


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