From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "andrés ramírez" <rrandresf@hotmail.com>
Cc: 57364@debbugs.gnu.org
Subject: bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY
Date: Fri, 26 Aug 2022 09:07:37 +0800 [thread overview]
Message-ID: <87pmgnu812.fsf@yahoo.com> (raw)
In-Reply-To: <SJ1PR12MB6363953D59C4E5950A79C6A7A6729@SJ1PR12MB6363.namprd12.prod.outlook.com> ("andrés ramírez"'s message of "Thu, 25 Aug 2022 15:13:14 +0000")
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?
next prev parent reply other threads:[~2022-08-26 1:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 17:51 bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY Andrés Ramírez
2022-08-24 1:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25 14:29 ` andrés ramírez
2022-08-25 15:13 ` andrés ramírez
2022-08-26 1:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-26 1:50 ` andrés ramírez
2022-08-26 3:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 3:43 ` andrés ramírez
2022-08-26 5:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 13:59 ` andrés ramírez
2022-08-27 1:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 19:58 ` andrés ramírez
2022-08-30 1:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 5:28 ` andrés ramírez
2022-08-30 7:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 7:29 ` bug#57364: [PATCH] (was: bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY) andrés ramírez
2022-08-30 10:07 ` bug#57364: [PATCH] Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-27 12:49 ` bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY Lars Ingebrigtsen
2022-09-27 13:46 ` andrés ramírez
2022-09-27 17:32 ` Lars Ingebrigtsen
2022-08-30 8:02 ` bug#57364: 28.1; emacs segfaulted when debugging emacs form within emacs for bug#57364 Andrés Ramírez
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmgnu812.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=57364@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=rrandresf@hotmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).