From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Bad Protocol request 77 Date: Wed, 29 Jun 2005 12:41:19 -0400 Message-ID: References: <87fyv1d84x.fsf-monnier+emacs@gnu.org> <8DCDF4A8-1124-4F34-8C44-68BD7A647A31@swipnet.se> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1120063837 14670 80.91.229.2 (29 Jun 2005 16:50:37 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 29 Jun 2005 16:50:37 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 29 18:50:36 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DnflP-0004uO-F5 for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2005 18:50:15 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DnftU-0005dz-Gb for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2005 12:58:36 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dnfr1-0004oL-07 for emacs-devel@gnu.org; Wed, 29 Jun 2005 12:56:03 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dnfqw-0004kd-Bw for emacs-devel@gnu.org; Wed, 29 Jun 2005 12:55:59 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dnfqt-0004YA-TD for emacs-devel@gnu.org; Wed, 29 Jun 2005 12:55:56 -0400 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DnfhX-0000cD-B8 for emacs-devel@gnu.org; Wed, 29 Jun 2005 12:46:15 -0400 Original-Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 526352CF416; Wed, 29 Jun 2005 12:41:24 -0400 (EDT) Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id DDCE54AC00F; Wed, 29 Jun 2005 12:41:19 -0400 (EDT) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id C21D1E6C19; Wed, 29 Jun 2005 12:41:19 -0400 (EDT) Original-To: jhd In-Reply-To: <8DCDF4A8-1124-4F34-8C44-68BD7A647A31@swipnet.se> (jhd's message of "Wed, 29 Jun 2005 17:05:03 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.846, requis 5, autolearn=not spam, AWL 0.05, BAYES_00 -4.90) X-MailScanner-From: monnier@iro.umontreal.ca X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:39895 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:39895 >> 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