Re: libperleditor bug (was Re: Perl-Qt Designer Plugin ?)

Germain Garand wrote:

>>Qt does a:
>>XCreateFontSet(dpy, fontsetnames[i], &missList, &missCount, 0);
>>with fontsetnames[i]= "-*-fixed-medium-i-*-*-16-*,-*-*-medium-i-*-*-16-*"
>>in getFontSet in qinputcontext_x11.cpp
>>
>>and despite:
>>
>>$ xlsfonts -fn "-*-fixed-medium-i-*-*-16-*"
>>xlsfonts: pattern "-*-fixed-medium-i-*-*-16-*" unmatched
>>$ xlsfonts -fn "-*-*-medium-i-*-*-16-*"
>>- -dustin-dustismo roman-medium-i-normal-bold italic-16-0
>>    
>>
>[...]
>  
>
>>I still get a SIGSEGV <sigh>
>>
>>Sorry for the noise :)
>>    
>>
>
>and then how did you fix it? Is that a Qt bug?
>  
>
I don't think so*.
*All the parameters to XCreateFontSet() seem valid. I suspect my fonts. 
I do think it might be a bug in X (which shouldn't segfault no matter 
what is passed or what weird (and maybe broken) fonts I install). Now I 
have a test case maybe I'll try building that today... (gulp 62Mb of 
source...) ;)

to fix it I turneded off italic in conf.cpp
-    s.font = QFont( commentFamily, normalSize, normalWeight, TRUE );
+    s.font = QFont( commentFamily, normalSize, normalWeight );

It's not the font as such. The xfontset cache code is triggered the 
Qfont bold/italic/size.

On my system if I choose an italic font in designer C++ prefs it 
exhibits the same behaviour and segfaults after typing in /*
This doesn't happen in other Qt applications though - ???

I'll see if I can put a simple Qt test case together.

David