On Wed, 17 Jun 2009, Albrecht Schlosser wrote: >> In my FLTK application, I'm getting a segfault.
I have rolled back to an earlier version of the application which solved the immediate problem. >> Yesterday when I tried tracing with >> gdb, the backtrace indicated a problem in XLoadQueryFont >> (called through fl_font -> fl_xxfont if I recall >> correctly) >> >> I tried updating my 1.1.7 FLTK to 1.1.9 and still get >> the same segfault, however when I try to run the program >> through gdb now, I'm getting a segfault at a much earlier >> stage. Anti-aliasing fonts somehow is switched off now all of a sudden, which makes me think that some update to my system must have dropped some dependency. > Did you try FLTK 1.3 ? [..] I remember that some > uninitialized font-related variables (internal display > handles or similar) have been fixed. I'll take a look at it. >> Is there anything I can do about [different >> production/gdb behaviour]? > If you can, try running your program with valgrind > (on Linux). Recently someone had a bug, and the > valgrind output showed a hint that an object had > been deleted before it should have been. Thanks, I'll see what that brings up. Best, Marc _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
