From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Unknown Newsgroups: gmane.emacs.bugs Subject: bug#37895: 26.3; X protocol error: BadLength (poly request too large or internal Xlib length error) on protocol request 139 Date: Thu, 24 Oct 2019 17:34:00 +0200 Message-ID: <2bc605b7f4bce3cdf8a705b31ba8b1667cfe461b.camel@gmx.de> References: <76051a354c8fe7d23632226f5b51d93233c3c522.camel@gmx.de> <83k18uxn29.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="262911"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Evolution 3.34.1 Cc: 37895@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Oct 24 18:27:38 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iNfxa-0016F3-7z for geb-bug-gnu-emacs@m.gmane.org; Thu, 24 Oct 2019 18:27:38 +0200 Original-Received: from localhost ([::1]:46830 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNfxY-0005ZY-6b for geb-bug-gnu-emacs@m.gmane.org; Thu, 24 Oct 2019 12:27:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48809) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNf8i-0003sP-M3 for bug-gnu-emacs@gnu.org; Thu, 24 Oct 2019 11:35:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNf8h-0006mc-BK for bug-gnu-emacs@gnu.org; Thu, 24 Oct 2019 11:35:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:56199) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iNf8g-0006m5-5A for bug-gnu-emacs@gnu.org; Thu, 24 Oct 2019 11:35:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iNf8f-0002DM-Vl for bug-gnu-emacs@gnu.org; Thu, 24 Oct 2019 11:35:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Unknown Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 24 Oct 2019 15:35:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 37895 X-GNU-PR-Package: emacs Original-Received: via spool by 37895-submit@debbugs.gnu.org id=B37895.15719312608452 (code B ref 37895); Thu, 24 Oct 2019 15:35:01 +0000 Original-Received: (at 37895) by debbugs.gnu.org; 24 Oct 2019 15:34:20 +0000 Original-Received: from localhost ([127.0.0.1]:36787 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iNf80-0002CE-Ft for submit@debbugs.gnu.org; Thu, 24 Oct 2019 11:34:20 -0400 Original-Received: from mout.gmx.net ([212.227.17.21]:56455) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iNf7u-0002Bp-EI for 37895@debbugs.gnu.org; Thu, 24 Oct 2019 11:34:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1571931243; bh=sDRERdkZv/SIiisXCwMr4WcaBltMU+87Tjl9u1BSncw=; h=X-UI-Sender-Class:Subject:From:To:Cc:Date:In-Reply-To:References; b=EYKng6d1F0y587CosEt/uz44AYcLB4g9gzkBP5O2Hst/5D0oUK9VdgAj+OB6q8UNp 2H6K5cArPfjQfy5o4oAq68Fkr5ELXRS4lRopOqkpHxoDgg0WikuDON587brGi76R9v kPr4a7bTLMQNrBc1zDjN324okGg2+3Vmk+tqdLRI= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from venla ([134.169.54.114]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N17UQ-1hzqvx1YYk-012W06; Thu, 24 Oct 2019 17:34:03 +0200 In-Reply-To: <83k18uxn29.fsf@gnu.org> X-Provags-ID: V03:K1:XQRzxEZQIn4oFzotu4OYGitaG2RfbTf+B3AJIvVXbMCJa/oiAgm qN9+bhQmsjkEmkA7Y1UeT7bDkKmEh+pGru15GZ8ApqonE4Zc+Refb5l6/uELuNmSAP6ygDY cGcSQ1KcE2kTSyIFqnop4DjJUq0Drc5Y53u4topJOA5ZkBV4t1+kRi8nEzv5V9vNi7fwHgi T6YosGQzc03/o6uZUWrpQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:PN59baMSOR0=:X+MEK64ZmApsoUF7Dyh/OK u0VDv3yMGND9yDzu8IhZiD3m57Mgl4ghl+fbFBnIPFlqht1sQgog6QV7seKy0NGI7U58SV81M iAMfsHZ4p/OYMHItn02Kivgw/21YfIdegd29FB3uEyPji6PIL8YDt2lrP0DyZY+BmOWNvG/H1 YQSh7iUVBUwTlVnu1p9Jyqkx3QCt7UmVdGqBD86zCkjLI6PilNtZtIlygA4LTCXmjBlMkh5ts 6RNEJ/Ip10eJbdJKIYY2vaQ5/j/jmFR4ztlGi8otb+FR/SJtvBMOE4E8nRRd/p8Cm6uw0duEQ OAJkqsV7c0PKXvXzc1xRgoTXwgGB4er6Yj2Z4bFznXiNmbRZi/4lrZee/3SHCPmTwEcsrPnM2 DsEsBjIoJB3+V1Fk7D+3KSea2AWYdJZJpbTIUgMISCw57/u0WhBCZf+JzY/llMaGSZMCbLpaH IDqmW3Q+9cuxdcLKOHEobGcaYPGseNN7i+0kOm/AKBCJHt4MVM1smUt0kQdlwMEiz24eXf7Q/ +VAVFtWNYsLKSjMf5YhDFd2fQPqPv1Xw/FO3hsyEFsGSy3HeW9LTs/+0139/eYHvdlEAHiOsW my3RxbAa16UsTWWD6vTlFEZhB8XiIQs6UOoFxJXqPIpCRRLxlU7vXdMFx9qpYHgncpjp6Mj/5 ATpgIhKx7ghKPZRji0Sdt7KxenV77u+cFKHo1jia4cJdElg1N7xdj2Ol9ky/HGI6Qz7D2AAlL R/3LPIAIsO8DTEmXG2gNJwVhcYHPB9hi3/8Os9ZLAYzDVLDiMDcmAvUKsaorNgomfFPfWO08 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:170136 Archived-At: On Thu, 2019-10-24 at 16:58 +0300, Eli Zaretskii wrote: > > From: Unknown > > Date: Thu, 24 Oct 2019 00:14:13 +0200 > > > > Emacs crashes after triggering an X error message. > > > > To reproduce the error, I have to start emacs as a daemon via > > > > > emacs --fg-daemon > > > > and a client via > > > > > emacsclient -create-frame --alternate-editor=3D"" > > > > As soon as I open a source file (C++ in my case), emacs crashes > > immediately based on the following X error: > > Does this happen with _any_ file or just some? If the latter, can > you > try to figure out what is special about those files? > > If this happens with any file, does it also happen with pure ASCII > files, like the README files in the Emacs distribution? No, if I open the README, then everything works normally. > > > Note: the bug seems to be very similar to the > > one reported here: > > > > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D30874#33 > > > > My emacs is (naturally) heavily modded, and I was not able to > > pinpoint > > the problem to one concrete package. Noticably, I *can* enter the > > unicode symbol 274c. > > The backtrace seems to indicate that Emacs crashed trying to open > some > font, so tracing the fonts Emacs loads might give a hint wrt what > goes > wrong. I have not included any additional fonts myself, but I guess the theme does. Regarding the tracing: As far as I can see the bottommost emacs code being called is static Lisp_Object xftfont_open (struct frame *f, Lisp_Object entity, int pixel_size) I also got (gdb) call debug_print(entity) # Does that help? > > Thanks.