GNU bug report logs -
#63589
29.0.91; crash after creating graphical frames via emacsclient when compiled with cairo-xcb
Previous Next
Full log
Message #17 received at 63589 <at> debbugs.gnu.org (full text, mbox):
Thiago Melo <tmdmelo <at> gmail.com> writes:
> I must also highlight that the following errors in the backtrace
> happen one right after the other (i.e., I'm unable to interact with
> the zombie emacs frame in between).
Yes, I know. Thanks.
> ```
> Breakpoint 2, x_error_quitter (display=0x55555654f4f0,
> event=0x7fffffff71c0) at xterm.c:26126
> 26126 if (event->error_code == BadName)
> (gdb) p *event
> $1 = {
> type = 0,
> display = 0x55555654f4f0,
> resourceid = 54526136,
> serial = 706,
> error_code = 14 '\016',
> request_code = 1 '\001',
> minor_code = 0 '\000'
> }
> (gdb) continue
> Continuing.
This means Emacs tried to create a window with an invalid XID. Would
you please show the backtrace from this error, now that Emacs is
operating synchronously?
> Breakpoint 2, x_error_quitter (display=0x55555654f4f0,
> event=0x7fffffff6a50) at xterm.c:26126
> 26126 if (event->error_code == BadName)
> (gdb) p *event
> $2 = {
> type = 0,
> display = 0x55555654f4f0,
> resourceid = 54526136,
> serial = 707,
> error_code = 3 '\003',
> request_code = 8 '\b',
> minor_code = 0 '\000'
> }
> (gdb) continue
> Continuing.
>
> Breakpoint 2, x_error_quitter (display=0x55555654f4f0,
> event=0x7fffffff6a50) at xterm.c:26126
> 26126 if (event->error_code == BadName)
> (gdb) p *event
> $3 = {
> type = 0,
> display = 0x55555654f4f0,
> resourceid = 54526136,
> serial = 708,
> error_code = 3 '\003',
> request_code = 12 '\f',
> minor_code = 0 '\000'
> }
> (gdb) continue
> Continuing.
> ```
These further errors are simply a result of the invalid window being
used.
This bug report was last modified 2 years and 19 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.