On Sat, 30 Mar 2013 13:03:22 +0100, Thomas Meyer wrote:
In the backtrace is:
#6 0x00007fffbe51c92e in WebKit::core () from /lib64/libwebkitgtk-1.0.so.0
#7 0x00007fffbe4ef8f8 in WebKit::GtkAdjustmentWatcher::updateAdjustmentsFromScrollbars ()
#8 0x00007fffbe4ef979 in updateAdjustmentCallback () from /lib64/libwebkitgtk-1.0.so.0
This means GDB could not find the /usr/lib/debug/**.debug file from
webkitgtk-debuginfo.rpm and GDB always complains about it. After you have
loaded the core file (or if it crashed under GDB etc.) GDB should also print
some such suggestion:
Missing separate debuginfos, use: debuginfo-install webkitgtk-1.10.2-3.fc18.x86_64
If you run this command more debug info should be evailable, primarily there
will be visible the source file+line for the 3 functions above
(and no longer the "from /lib64/...." text).
I wanted to recompile the webkitgtk package with
to hopefully get some more information what exactly is going on here:
This is higher level of debugging aid which should be used only if the default
debuginfo rpm is insufficient. But then if you recompile the rpm one should
primarily use -O0 (with default $RPM_OPT_FLAGS -g) in CFLAGS+CXXFLAGS there,
--enable-debug is also useful but IMO not so much as -O0 there.
But I'm not able to compile this package on my machine as the
linker step get's killed in OOM.
You could also use "fedpkg build --scratch --srpm" if you have Koji account.