GNU bug report logs - #73752
29.4; Ligatures are randomly rendered with extra spaces

Previous Next

Full log

Message #173 received at 73752 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Visuwesh <visuweshm <at> gmail.com>
Cc: dev <at> real-or-random.org, xuan <at> xlk.me, 73752 <at> debbugs.gnu.org
Subject: Re: bug#73752: 29.4; Ligatures are randomly rendered with extra spaces
Date: Thu, 31 Oct 2024 11:43:58 +0200

> From: Visuwesh <visuweshm <at> gmail.com>
> Cc: Tim Ruffing <dev <at> real-or-random.org>,  73752 <at> debbugs.gnu.org,  xuan <at> xlk.me
> Date: Thu, 31 Oct 2024 13:42:06 +0530
> 
> > Did the "bad" display start from "good" at the beginning of a session?
> > Or did it start from "bad" to begin with?  If the former, the next
> > idea is to put a watchpoint on the cached composition in a session
> > with "good" display, and then do whatever it takes to make it "bad",
> > hoping that the watchpoint will break at some point and show us the
> > code which replaces nil with these [X-OFF Y-OFF WADJUST] vectors.
> 
> I think it starts from "bad" to begin with.  But the former theory could
> still apply, if you do not mind this vague answer, can you provide
> instructions to set a watchpoint?  If the watchpoint never triggers, we
> might be able to at least rule out the former theory.

Let's first see if a breakpoint inside
composition_gstring_adjust_zero_width ever breaks in your cases.  If
it doesn't we will try the watchpoint technique.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.