From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Bad Protocol request 77
Date: Wed, 29 Jun 2005 12:41:19 -0400 [thread overview]
Message-ID: <jwv7jgddslg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8DCDF4A8-1124-4F34-8C44-68BD7A647A31@swipnet.se> (jhd's message of "Wed, 29 Jun 2005 17:05:03 +0200")
>> My Emacs is crashing in Gnus when displaying some articles.
>> I haven't been able to get a reliable recipe yet, but basically I get
>> a backtrace as shown in the appended session.
>> The first backtrace is with x-synchronize turned off, the second is with
>> x-synchronize turned on.
>>
>> Could give me some hint what I should be looking at?
>> In the mean time, I'll try to get a reliably reproducible recipe.
>>
>>
>> Stefan
>>
>>
>> (gdb) bt
>> #0 x_error_quitter (display=0xbfffce30, error=0xbfffcd00) at
>> xterm.c:7788
>> #1 0x0810175c in x_error_handler (display=0x8714568, error=0xbfffcd00)
>> at xterm.c:7753
>> #2 0xb7ddf624 in _XError () from /usr/X11R6/lib/libX11.so.6
> Can you print out the error string (error parameter to x_error_handler)?
> 77 is just XDrawImageString16 which is in the second backtrace as expected.
> But it can generate different errors. I think it is a BadMatch, which
> usually indicates bad input to XDrawImageString16. You should be able to
> walk up to the stack frame that calls XDrawImageString16 and examine
> the input.
It's indeed a BadMatch, but I don't know what part of the input would be
interesting to examine or what legitimate values should look like,
Stefan
next prev parent reply other threads:[~2005-06-29 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 5:53 Bad Protocol request 77 Stefan Monnier
2005-06-29 6:06 ` Stefan Monnier
2005-06-29 15:05 ` jhd
2005-06-29 16:41 ` Stefan Monnier [this message]
2005-07-01 10:05 ` jhd
2005-07-01 15:19 ` Stefan Monnier
2005-07-01 17:58 ` jhd
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv7jgddslg.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.