bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY

[Po Lu]

andrés ramírez <rrandresf@hotmail.com> writes:

> * new backtrace on x_error_handler
> Thread 1 "emacs" hit Breakpoint 4, x_error_handler (display=0x5555560e8370, 
> event=0x7fffffffb520) at ../../src/xterm.c:10270
> 10270   if (x_error_message)
> (gdb) bt
> #0  x_error_handler (display=0x5555560e8370, event=0x7fffffffb520) at 
> ../../src/xterm.c:10270
> #1  0x00007ffff7bf433c in _XError (dpy=dpy@entry=0x5555560e8370, 
> rep=rep@entry=0x5555567ba850) at XlibInt.c:1503
> #2  0x00007ffff7bf0e58 in handle_error (dpy=0x5555560e8370, 
> err=0x5555567ba850, in_XReply=<optimized out>) at xcb_io.c:211
> #3  0x00007ffff7bf0ef5 in handle_response (dpy=dpy@entry=0x5555560e8370, 
> response=0x5555567ba850, in_XReply=in_XReply@entry=1) at xcb_io.c:403
> #4  0x00007ffff7bf20bd in _XReply (dpy=dpy@entry=0x5555560e8370, 
> rep=rep@entry=0x7fffffffb6e0, extra=extra@entry=0, discard=discard@entry=1) 
> at xcb_io.c:722
> #5  0x00007ffff7bed5f1 in XSync (dpy=0x5555560e8370, discard=0) at Sync.c:44
> #6  0x00005555557059c1 in x_catch_errors_with_handler (dpy=0x5555560e8370, 
> handler=0x0, handler_data=0x0) at ../../src/xterm.c:10015
> #7  0x0000555555705a37 in x_catch_errors (dpy=0x5555560e8370) at 
> ../../src/xterm.c:10028

This still isn't a usable backtrace, since the error is being reported
by an explicit call to XSync, sorry.

Are you sure you enabled X synchronization correctly?