On Sat, 30 Mar 2013 21:05:08 +0100, Thomas Meyer wrote:
I already have the debuginfo packages installed:
This was explained by Rex Dieter, it is due to -g1 used from webkitgdb.spec:
# Build with -g1 on all platforms to avoid running into 4 GB ar format limit
#
https://bugs.webkit.org/show_bug.cgi?id=91154
%global optflags %(echo %{optflags} | sed 's/-g /-g1 /')
This -g1 workaround is already disabled in Rawhide (and expecting also F-19):
https://bugzilla.redhat.com/show_bug.cgi?id=861452
With F-19+ the standard debuginfo rpm should be sufficient for the backtrace:
(gdb) p 'WebKit::GtkAdjustmentWatcher::updateAdjustmentsFromScrollbars()'
$1 = {<text variable, no debug info>} 0x3eaca0
<WebKit::GtkAdjustmentWatcher::updateAdjustmentsFromScrollbars()>
(gdb) info line *0x3eaca0
Line 60 of "Source/WebKit/gtk/WebCoreSupport/GtkAdjustmentWatcher.cpp"
starts at address 0x3eaca0
<WebKit::GtkAdjustmentWatcher::updateAdjustmentsFromScrollbars()>
and ends at 0x3eaca9
<WebKit::GtkAdjustmentWatcher::updateAdjustmentsFromScrollbars()+9>.
(That <text variable, no debug info> seems as a GDB bug to me.)
okay. But i guess I'm also not able to do this on my machine, as
4GiB
main memory is too few for the final linking step!
Or will it compile with -O0 with 4GiB RAM?
-O0 may have lower GCC memory requirements but I really do not know.
> You could also use "fedpkg build --scratch --srpm" if
you have Koji account.
Where do I get a Koji account?
Google is your friend.
Regards,
Jan