On Mon, Dec 31, 2018 at 02:32:58PM -0500, Thomas Dickey wrote: > On Mon, Dec 31, 2018 at 06:11:23PM +0100, Alexander Meyer wrote: > > * Thomas Dickey <dic...@his.com> [2018-12-31 00:51]: > > > > > On Sun, Dec 30, 2018 at 06:26:44PM +0100, Alexander Meyer wrote: > > > ... > > >> This is the behaviour I get across xterm versions: > > >> (everything with libfontconfig1 2.13.1-2) > > >> > > >> fonts.conf enabled: > > >> 337: works > > >> 338: segfault > > >> 340: segfault > > >> 341: segfault > > > > > > Can you make a backtrace for #341, please? > > > > Here it is: > > thanks. I added some notes, but have not been able to reproduce the problem.
Looking at this again, I saw (using XFT_DEBUG=3 and the -report-fonts option) that the fallback was using unifont. Removing that got it to break (I'll see whether the bug lies in Xft or fontconfig, at least). -- Thomas E. Dickey <dic...@invisible-island.net> https://invisible-island.net ftp://ftp.invisible-island.net
signature.asc
Description: Digital signature
