Hi. I thought that I was not able to reproduce this bug, but discovered that it only occurs when qalculate-gtk is compiled with optimizations. qalculate-gtk does not only segfault when pressing Down twice, but whenever the expression entry has lost focus and tries to take it back when some interesting key has been pressed.
I have yet to find a good solution. For now the alternatives are to compile qalculate-gtk without optimizations or comment out lines 12894-12900 in src/callbacks.cc (responsible for reclaiming expression entry focus). On Sunday 7 January 2007 22:41, Martin Waitz wrote: > hoi :) > > The debian Bug Tracking System has a report on a segfault in > qalculate-gtk: http://bugs.debian.org/404241 > It got reported agains 0.9.4 but also affects 0.9.5. > > It is quite easy to reproduce: start qalculate-gtk and hit <Arrow-Down> > two times. > > (gdb) bt > #0 0x41c70000 in ?? () > #1 0xb7d5325f in _gtk_marshal_BOOLEAN__BOXED () > from /usr/lib/libgtk-x11-2.0.so.0 > #2 0xb761698b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 > #3 0xb7626f2d in g_signal_chain_from_overridden () > from /usr/lib/libgobject-2.0.so.0 > #4 0xb7628208 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 > #5 0xb76285d9 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 > #6 0xb7e3ce84 in gtk_widget_get_default_style () > from /usr/lib/libgtk-x11-2.0.so.0 > #7 0xb7d4cc0a in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0 > #8 0xb7d4de07 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 > #9 0xb7be5eea in _gdk_events_init () from /usr/lib/libgdk-x11-2.0.so.0 > #10 0xb733ab21 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 > #11 0xb733db96 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 > #12 0xb733df57 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 > #13 0xb7d4e281 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 > #14 0x080664d3 in main (argc=Cannot access memory at address 0xa > ) at main.cc:293 > > the 0xb7d5325f inside _gtk_marshal_BOOLEAN__BOXED is the return address > after a call to g_value_set_boolean which then seems to wrack havoc. > > But unfortunately I don't know how to debug this thing deeper to find > the corrupt signal that gets emitted. > > Can you help? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
