From: "Francesco Potortì" <pot@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44930@debbugs.gnu.org
Subject: bug#44930: I can reproduce it
Date: Tue, 01 Dec 2020 18:19:54 +0100 [thread overview]
Message-ID: <E1kk9Ji-00BycL-VL@tucano.isti.cnr.it> (raw)
In-Reply-To: <83pn3timo4.fsf@gnu.org> (eliz@gnu.org)
>> In this moment I have a *w3m* buffer on a live Emacs. If I switch to it
>> on a text frame, everything is well. If I switch to it on an X display,
>> the frame dies (but Emacs survives). The error is
>>
>> X protocol error: BadMatch (invalid parameter attributes) on protocol request 73
>>
>> until I don't kill the buffer, I can reproduce the error at will. I
>> have no idea how to debug it. If I am instructed, I can try until Emacs
>> is alive.
>
>etc/DEBUG has some instructions for debugging X protocol errors;
>search for "If you encounter X protocol errors".
Ok. I fear I will not be able to do that quickly.
>In addition to what that says, it would be beneficial to understand
>what kind of X request is "request 73".
According to http://www.rahul.net/kenton/xproto/xrequests.html 73 is the
X protocol GetImage call.
According to https://www.x.org/wiki/guide/concepts/#index2h3, this is seldom
used, for example for making screenshots or for redrawing. The second
usage could explain why it happens when I switch buffer and why the
debugger points to the internal C function redisplay_internal()
The XGetImage function is called twice from gtkutil.c and thrice from
image.c, so one of these is apparently failing.
According to
https://www.x.org/releases/X11R7.7/doc/xproto/x11protocol.html#requests:GetImage
the call may return a Match error when the pixmap or window to be
returned do not satisfy certain geometric criteria.
This is strange, because the error happens only when I switch to a
specific buffer, which makes me think that it depends on the buffer
contents. Is there a way to save the buffer contents including
attributes (fonts, overlays and other things that I do not know about)
to disk, so that I can easily recreate a buffer with the strange
property of causing this error?
next prev parent reply other threads:[~2020-12-01 17:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 19:36 bug#44930: 27.1; X protocol error: BadMatch (...) on protocol request 73 Francesco Potortì
2020-11-30 21:46 ` bug#44930: I can reproduce it Francesco Potortì
2020-12-01 15:14 ` Eli Zaretskii
2020-12-01 17:19 ` Francesco Potortì [this message]
2020-12-01 18:29 ` Eli Zaretskii
2020-12-02 4:28 ` Richard Stallman
2020-12-05 16:08 ` Francesco Potortì
2020-12-05 19:44 ` Alan Third
2020-12-05 22:44 ` Francesco Potortì
2020-12-12 10:43 ` Alan Third
2020-12-12 13:09 ` Francesco Potortì
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=E1kk9Ji-00BycL-VL@tucano.isti.cnr.it \
--to=pot@gnu.org \
--cc=44930@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).