From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: Display problems with non-ascii characters Date: Tue, 14 Oct 2008 20:49:39 +0900 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=ISO-2022-JP-2 X-Trace: ger.gmane.org 1223985004 7337 80.91.229.12 (14 Oct 2008 11:50:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 14 Oct 2008 11:50:04 +0000 (UTC) Cc: emacs-devel@gnu.org To: Sascha Wilde Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 14 13:51:02 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KpiQY-0008TJ-92 for ged-emacs-devel@m.gmane.org; Tue, 14 Oct 2008 13:51:02 +0200 Original-Received: from localhost ([127.0.0.1]:34751 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KpiPT-0006qL-Qv for ged-emacs-devel@m.gmane.org; Tue, 14 Oct 2008 07:49:55 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KpiPP-0006py-6N for emacs-devel@gnu.org; Tue, 14 Oct 2008 07:49:51 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KpiPO-0006pc-2g for emacs-devel@gnu.org; Tue, 14 Oct 2008 07:49:50 -0400 Original-Received: from [199.232.76.173] (port=41478 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KpiPN-0006pW-Ox for emacs-devel@gnu.org; Tue, 14 Oct 2008 07:49:49 -0400 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:37439) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KpiPM-0004Vw-VM for emacs-devel@gnu.org; Tue, 14 Oct 2008 07:49:49 -0400 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id m9EBngHj015668; Tue, 14 Oct 2008 20:49:42 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp1.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id m9EBnfrV014282; Tue, 14 Oct 2008 20:49:41 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp1.aist.go.jp with ESMTP id m9EBndFN028938; Tue, 14 Oct 2008 20:49:39 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.69) (envelope-from ) id 1KpiPD-0001aG-8l; Tue, 14 Oct 2008 20:49:39 +0900 In-reply-to: (message from Sascha Wilde on Tue, 14 Oct 2008 11:14:16 +0200) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) X-detected-operating-system: by monty-python.gnu.org: Solaris 9 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:104512 Archived-At: In article , Sascha Wilde writes: > I'm not intending to be a pita, but this is still an issue and I think > it should be further investigated and resolved. Thank you for keeping on attacking this problem. But... > If I can help, by sending debugger info or the like please tell me what > to do. as the reported phenomenon is so mysterious that I can't think of any good debugging strategy. :-( > On a second thought I think that my statement: > > So It seems the problem might really be a strange X11 bug, which is > > triggered by the new Emacs display code? > is somewhat to much of an excuse: The problem really only shows with > recent Emacs, not with any other application where I'm using exactly the > same fonts, nor with older (22) Emacsn. > More additional information, I don't know if its useful but it might > contain some hints for those who know the dirty details of Emacs > display... ;-) > I noticed the following phenomenon (which is really an extended version > of my observations from the last mail): > I have two systems, A and B, and two users foo and bar, they both have > access to the very same Emacs binary (over nfs) and they both can use > the same X display (via ssh -X). > My X-server runs an system A. > 1. I start Emacs with -Q as user bar on system B and do my C-h H test. > No problem when changing the default font to terminus. > After that I quit Emacs. > 2. I start Emacs as user foo on system A and do some work, until the > "vanished special chars" bug shows up. I keep that Emacs running and > ... > 3. ... start again Emacs -Q as bar on system B and do my C-h H test. > After changing the default font to terminus the umlauts are vanished > in this instance of Emacs, too! > Please note that the only thing the two Emacsn have in common is the > X Display, as they run on different hosts by different users. > 4. Now: when I quit both Emacsn and restart at 1. the bug is gone again! > So it affects all Emacsn on the same display once it appeared, but it > "heals" again when all affected Emacsn are closed... > Any ideas? Insights? Suggestions on how to proceed debugging this? As far as I can't reproduce the problem, I think there's no way other than you debug Emacs by gdb. As you wrote: ---------------------------------------------------------------------- C-u C-x = on the vanished `$(D)N(B' shows: [...] x:-xos4-terminus-medium-r-normal--16-160-72-72-c-80-iso10646-1 (#xDF) ---------------------------------------------------------------------- Please find a way to reproduce the problem with a buffer that contains only "$(D)N(B". Then, run Emacs under gdb as this: % cd .../src/emacs % gdb emacs (gdb) br xfont.c:833 (gdb) cond 3 len==1&& s->char2b.byte2==0xDF (gdb) run and repeat the above procedure. Emacs should stop at line 841. Then try this and see how screen changes: (gdb) ff (gdb) fin (gdb) ff See also emacs/etc/DEBUG. It has many hints for debugging Emacs with gdb. --- Kenichi Handa handa@ni.aist.go.jp