On 2/14/08, Joe English <[EMAIL PROTECTED]> wrote: > > Remi Vanicat wrote: > > > with xmaxima: > > #0 0x00002b10c17f9c4d in GetTkFontAttributes (ftFont=0x0, faPtr=0xaa8b58) > > at /home/sergei/debian/tcl-2/tk8.5-8.5.1/unix/../unix/tkUnixRFont.c:107 > > #1 0x00002b10c17fa0b6 in InitFont (tkwin=0xab1240, pattern=0xacaa90, > > fontPtr=0xaa8b20) > > at /home/sergei/debian/tcl-2/tk8.5-8.5.1/unix/../unix/tkUnixRFont.c:241 > > #2 0x00002b10c17fa450 in TkpGetFontFromAttributes (tkFontPtr=0x0, > > tkwin=0xab1240, faPtr=0x7fffe95f1500) > > at /home/sergei/debian/tcl-2/tk8.5-8.5.1/unix/../unix/tkUnixRFont.c:369 > > [...] > > > This is probably the same as Tk bug #1090382 [*]. > It appears to be caused by a misconfigured fontconfig > system; running `fc-cache -fv` should fix it.
For me it looks very strange that tkFontPtr is NULL in #2 and fontPtr is not NULL in #1. The relevant code is: fontPtr = (UnixFtFont *) tkFontPtr; if (fontPtr != NULL) { FinishedWithFont(fontPtr); } fontPtr = InitFont(tkwin, pattern, fontPtr); I can't explain the fact that fontPtr isn't NULL other than by a bug in GCC. -- Sergei Golovan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]