unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Fri, 15 Mar 2024 10:37:13 -0600	[thread overview]
Message-ID: <8790adce-e863-46f8-bbaf-25660a917e04@emvision.com> (raw)
In-Reply-To: <87wmq4t2rp.fsf@yahoo.com>

On 3/15/24 12:42 AM, Po Lu wrote:
> Ali Bahrami <ali@emvision.com> writes:
> 
>> I'm running it as 'src/emacs', out of the workspace
>> that I built with the patch applied, as well as configured
>> with --without-xinput2. Did I miss a step, or should I be
>> running it differently?
> 
> Nevermind, the code to print this information wasn't installed in the
> Emacs 29 branch, being written awfully close to the time of the release.
> 
> Please apply this patch and respond with the error message the patched
> Emacs generates:
> 
> diff --git a/src/xterm.c b/src/xterm.c
> index acb008475c7..9f6d5196720 100644
> --- a/src/xterm.c
> +++ b/src/xterm.c
> @@ -26300,8 +26300,10 @@ x_error_handler (Display *display, XErrorEvent *event)
>   static void NO_INLINE
>   x_error_quitter (Display *display, XErrorEvent *event)
>   {
> -  char buf[256], buf1[400 + INT_STRLEN_BOUND (int)
> -		      + INT_STRLEN_BOUND (unsigned long)];
> +  char buf[256], buf1[800 + INT_STRLEN_BOUND (int)
> +		      + INT_STRLEN_BOUND (unsigned long)
> +		      + INT_STRLEN_BOUND (XID)
> +		      + INT_STRLEN_BOUND (int)];
>   
>     /* Ignore BadName errors.  They can happen because of fonts
>        or colors that are not defined.  */
> @@ -26314,8 +26316,12 @@ x_error_quitter (Display *display, XErrorEvent *event)
>   
>     XGetErrorText (display, event->error_code, buf, sizeof (buf));
>     sprintf (buf1, "X protocol error: %s on protocol request %d\n"
> -	   "Serial no: %lu\n", buf, event->request_code,
> -	   event->serial);
> +	   "Serial no: %lu\n"
> +	   "Failing resource ID (if any): 0x%lx\n"

> +	   "This is a bug!  Please report this to bug-gnu-emacs@gnu.org!\n"
> +	   buf, event->request_code, event->serial, event->resourceid,
> +	   event->minor_code);
>     x_connection_closed (display, buf1, false);
>   }



    This output is from emacs-x with both patches
applied:

     % src/emacs
     X protocol error: BadDrawable (invalid Pixmap or Window parameter) on protocol request 134
     Serial no: 1318
     Failing resource ID (if any): 0x5901a002
     Minor code: 14
     This is a bug!  Please report this to bug-gnu-emacs@gnu.org!

Note that I had to move the comma at the end of

     > +	   "Minor code: %d\n",

to the end of the following line. I only mention it in case
it's a sign that something else was intended.

Standing by for the next iteration. Thank you!

- Ali






  reply	other threads:[~2024-03-15 16:37 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
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 [this message]
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=8790adce-e863-46f8-bbaf-25660a917e04@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).