As far as the segfault itself, it had nothing to do with the font. Plib
does not segfault if it can't match the font (I checked). The problem is
that the string for that item was beyond plib's current limit of 80 characters
per char[]. David has a fix in his Inbox that truncates before
Jim Wilson writes:
David Megginson [EMAIL PROTECTED] said:
The problem is in PUI and/or the prop picker -- the font we're
currently using does not seem to have a '|' character in it, and that
must be throwing something off. Here's what gdb says:
0x082bceab in puFont::getStringWidth(char
Actually I would call this a FGFS problem in that FGFS is
asking for a character that is not present in the PLib font
that is being used. The PLib Font system does not claim
to be a universal font renderer in fact just the oposite in that
it gives you only the characters that it can pack
Cameron Moore writes:
With that latest CVS of FG and SG, I get a pretty critical segfault
when trying to use the property viewer to view the /sim/logging/
node. The httpd interface seems to work fine.
The problem is in PUI and/or the prop picker -- the font we're
currently using does not
With that latest CVS of FG and SG, I get a pretty critical segfault when
trying to use the property viewer to view the /sim/logging/ node. The
httpd interface seems to work fine.
After the segfault, no OpenGL apps work until I restart X. Tried
running fgfs through gdb but all I got was this:
