From: Ali Bahrami <ali_gnu2@emvision.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 69762@debbugs.gnu.org
Subject: bug#69762: X11 versions of Emacs 29 on sparc fail at startup
Date: Thu, 14 Mar 2024 19:48:43 -0600 [thread overview]
Message-ID: <e211750a-ea53-4135-bfef-7922f1383ea8@emvision.com> (raw)
In-Reply-To: <87frwtuymr.fsf@yahoo.com>
On 3/14/24 12:16 AM, Po Lu wrote:
> Ali Bahrami <ali_gnu2@emvision.com> writes:
>
>> On 3/13/24 6:17 PM, Po Lu wrote:
>>> Please run Emacs under gdb (or some other suitable debugger, e.g. dbx)
>>> with the command-line options:
>>> -q -xrm 'Emacs.synchronous: True'
>>> exactly as written above, break on xterm.c:x_error_quitter, and
>>> reply
>>> with the backtrace generated after this breakpoint is hit.
>>
>> The gdb output follows. Thanks.
>
> Thanks. Does this resolve the problem?
>
> diff --git a/src/xterm.c b/src/xterm.c
> index c8a43785564..55aba5b8604 100644
> --- a/src/xterm.c
> +++ b/src/xterm.c
> @@ -7297,11 +7297,11 @@ x_sync_init_fences (struct frame *f)
> /* The drawable given below is only used to
> determine the screen on which the fence is
> created. */
> - FRAME_X_WINDOW (f),
> + FRAME_OUTER_WINDOW (f),
> False);
> output->sync_fences[1]
> = XSyncCreateFence (FRAME_X_DISPLAY (f),
> - FRAME_X_WINDOW (f),
> + FRAME_OUTER_WINDOW (f),
> False);
>
> XChangeProperty (FRAME_X_DISPLAY (f), FRAME_OUTER_WINDOW (f),
I'm afraid not. I get the same result as before:
% src/emacs
X protocol error: BadDrawable (invalid Pixmap or Window parameter) on protocol request 134
Serial no: 1318
- Ali
next prev parent reply other threads:[~2024-03-15 1:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 17:57 bug#69762: X11 versions of Emacs 29 on sparc fail at startup ali_gnu2
2024-03-13 0:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-13 17:02 ` ali_gnu2
2024-03-14 0:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-14 5:56 ` Ali Bahrami
2024-03-14 6:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 1:48 ` Ali Bahrami [this message]
2024-03-15 2:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 4:22 ` Ali Bahrami
2024-03-15 6:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 16:37 ` Ali Bahrami
2024-03-16 0:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-16 4:58 ` Ali Bahrami
2024-03-16 6:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-16 6:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-17 1:13 ` Ali Bahrami
2024-03-16 11:14 ` Eli Zaretskii
2024-03-16 12:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-17 1:38 ` ali_gnu2
2024-03-17 11:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-23 17:00 ` Alan Coopersmith
2024-04-03 17:48 ` Alan Coopersmith via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 10:34 ` Eli Zaretskii
2024-04-06 11:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 16:36 ` ali_gnu2
2024-04-07 0:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=e211750a-ea53-4135-bfef-7922f1383ea8@emvision.com \
--to=ali_gnu2@emvision.com \
--cc=69762@debbugs.gnu.org \
--cc=luangruo@yahoo.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).