Your message dated Tue, 6 Mar 2012 17:31:16 -0600
with message-id <201203061731.17659.geissert@...>
and subject line Re: Bug#662738: frama-c: segfault when running frama-c-gui
has caused the Debian Bug report #662738,
regarding frama-c: segfault when running frama-c-gui
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@... immediately.)
I just found out about frama-c and wanted to give it a try. However:
The backtrace goes all the way to libQtGui.so.4 (I use the libqt4 gtk
engine) from the following:
#67 0xb7df61a2 in gtk_widget_show () from /usr/lib/libgtk-x11-2.0.so.0
#68 0x0858e787 in ml_gtk_widget_show ()
#69 0x084eb431 in camlGWindow__method_show_3683 ()
#70 0xb6690270 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
The rest is probably not very relevant, so I'm omitting it.
On Tuesday 06 March 2012 01:17:16 Stéphane Glondu wrote:
> Le 06/03/2012 07:00, Raphael Geissert a écrit :
> > The backtrace goes all the way to libQtGui.so.4 (I use the libqt4 gtk
> > engine) from the following:
> How to use the libqt4 gtk engine? Can you reproduce the bug with the
> standard gtk engine? (I cannot)
Apparently it's yet another one of qt4engine's bugs. Sorry for the noise.
(Answering your question: the engine is on the gtk-qt-engine package, and
you basically need to load /usr/share/themes/Qt4/gtk-2.0/gtkrc as part of
the gtkrc file.)