On Sun, 21 Aug 2011 07:33:36 -0500 (CDT) kqt4a...@comcast.net wrote: > I am using version 1.99z that I compiled a few days ago > If I press control-r while the mouse is over a component name I get a > segmentation fault
I have seen this recently too. I can't reproduce it exactly right now, but I do get weird garbage characters in the Report window that does pop up. Running with Valgrind gives a very long stream of these traces sometimes, but it depends on which component name I hover over: ==20085== Use of uninitialised value of size 8 ==20085== at 0x6E68010: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.2800.4) ==20085== by 0x12B71219: ??? (in /usr/lib/x86_64-linux-gnu/pango/1.6.0/modules/pango-basic-fc.so) ==20085== by 0x77A54A9: pango_shape (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.2800.4) ==20085== by 0x779891D: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.2800.4) ==20085== by 0x779928E: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.2800.4) ==20085== by 0x779B4C4: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.2800.4) ==20085== by 0x779C355: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.2800.4) ==20085== by 0x614C126: ??? (in /usr/lib/libgtk-x11-2.0.so.0.2400.4) ==20085== by 0x7EA2764: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.2800.6) ==20085== by 0x7EB37E2: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.2800.6) ==20085== by 0x7EBD257: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.2800.6) ==20085== by 0x7EBD60C: g_signal_emit_by_name (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.2800.6) ==20085== Regards, Colin _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user