SL fontconfig segfaults after updating to 2.5.0_rc1

[axel.roeslein@…]

Hello,

is just installed the latest 2.5.0_rc1 version through automatic update.

XQuartz launces and gives me a fresh xterm. If I execute "xterm" from the command line a segmentation fault is reported.

The crash report starts with:
Process:         xterm [20808]
Path:            /usr/X11/bin/xterm
Identifier:      xterm
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process:  bash [20806]

Date/Time:       2010-03-17 14:33:59.531 +0100
OS Version:      Mac OS X 10.6.2 (10C540)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000135d8a514900
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   libfontconfig.1.dylib               0x0000000100098343 FcStrListCreate + 59
1   libfontconfig.1.dylib               0x0000000100091e42 FcLangSetHasLang + 446
2   libfontconfig.1.dylib               0x000000010009390e FcCompareLang + 144
3   libfontconfig.1.dylib               0x00000001000934b3 FcCompareValueList + 460
4   libfontconfig.1.dylib               0x0000000100093726 FcCompare + 180
5   libfontconfig.1.dylib               0x0000000100094278 FcFontSetMatch + 312
6   libfontconfig.1.dylib               0x0000000100094485 FcFontMatch + 88
7   libXft.2.dylib                      0x000000010007681b XftFontMatch + 207
8   xterm                               0x00000001000151d6 xtermOpenXft + 73
9   xterm                               0x0000000100016df1 xtermComputeFontInfo + 538
10  xterm                               0x0000000100017368 xtermUpdateFontInfo + 64
11  xterm                               0x0000000100018670 xtermLoadFont + 3729
12  xterm                               0x000000010000ad68 VTRealize + 129
13  libXt.6.dylib                       0x0000000100152ce2 RealizeWidget + 399
14  libXt.6.dylib                       0x0000000100152e8b RealizeWidget + 824
15  libXt.6.dylib                       0x0000000100153017 XtRealizeWidget + 113
16  xterm                               0x0000000100009bb9 VTInit + 30
17  xterm                               0x000000010001c1a1 spawnXTerm + 1116
18  xterm                               0x000000010001e54d main + 3413
19  xterm                               0x00000001000016dc start + 52

Can anybody help with this?
Everything was fine up till version 2.5.0_beta2

Thanks,

Axel

[axel.roeslein@…]

Might be caused by my font configuration.

If I comment the line

XTerm*faceName: Monaco

from my ~/.Xdefaults file and restart the seg fault is gone.

[jeremyhu@…]

You're using the exact same xterm binary as before (/usr/X11/bin/xterm) which is from SnowLeopard (not XQuartz-2.5.0_rc1).

I cannot reproduce this problem (but I don't have the same /usr/X11 you do).

Can you please try running /opt/X11/bin/xterm directly.

After trying that, please do the following:

rm -rf ~/.fontconfig
/usr/X11/bin/font_cache -f
/usr/X11/bin/xterm

Did it work? Now do:

/opt/X11/bin/font_cache -f
/usr/X11/bin/xterm

Did it work?

[axel.roeslein@…]

Check 1: yes, /opt/X11/bin/xterm runs

Check 2: after font_cache rebuild with /usr/X11/bin/font_cache the /usr/X11/bin/xterm runs again without any seg fault

/opt/X11/bin/xterm runs too but doesn't use the font face I configured.

Check 3: after font_cache rebuild with /opt... the /usr xterm seg faults again

[jeremyhu@…]

Ok, it looks like the 10.6.2 fontconfig is crashing because it doesn't like the caches that are built by the newer fontconfig

[jeremyhu@…]

10.6.3 contains an updated fontconfig and should not have this problem