Summary: | net-firewall/fwbuilder - segfault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | PetaMem R&D <info> |
Component: | Current packages | Assignee: | Andreas K. Hüttel <dilfridge> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
PetaMem R&D
2011-08-06 20:06:35 UTC
The warning messages come from a bug in qt that was fixed in latest version 4.7.4: https://bugreports.qt.nokia.com//browse/QTBUG-16175 It normally doesn't seem to cause segfault however; could you provide a backtrace? http://www.gentoo.org/proj/en/qa/backtraces.xml I tried. make.conf CFLAGS="-D_FORTIFY_SOURCE=2 -march=core2 -mcx16 -msahf -msse4.1 --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=6144 -mtune=core2 -O2 -ftree-vectorize -pipe -ggdb" LDFLAGS="-s" #LDFLAGS="-Wl,-flto -Wl,--hash-style=gnu,-O1 -Wl,--as-needed" CXXFLAGS="${CFLAGS}" # This should not be changed unless you know exactly what you are doing. You # should probably be using a different stage, instead. CHOST="x86_64-pc-linux-gnu" FEATURES="splitdebug distcc" re-emerged fwbuilder $ gdb fwbuilder GNU gdb (Gentoo 7.2 p1) 7.2 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". For bug reporting instructions, please see: <http://bugs.gentoo.org/>... Reading symbols from /usr/bin/fwbuilder...(no debugging symbols found)...done. also, there is no /usr/lib/debug directory SO all I get is Starting program: /usr/bin/fwbuilder <args snipped> [Thread debugging using libthread_db enabled] Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.2/libstdc++.so.6.0.14-gdb.py", line 59, in <module> from libstdcxx.v6.printers import register_libstdcxx_printers ImportError: No module named libstdcxx.v6.printers [New Thread 0x7fffec8e5700 (LWP 5627)] [New Thread 0x7fffe1df3700 (LWP 5629)] Application asked to unregister timer 0x5c00001a which is not registered in this thread. Fix application. Application asked to unregister timer 0x73000015 which is not registered in this thread. Fix application. Program received signal SIGSEGV, Segmentation fault. 0x0000000000b98b0d in ?? () (gdb) q Maybe fwbuilder is one of these: "Note: Some packages unfortunately handle stripping by themselves, inside the upstream provided makefiles. This is an error and should be reported. All packages should leave Portage the task of the stripping or simply restrict stripping entirely. " Documentation about getting good backtraces is here: http://www.gentoo.org/proj/en/qa/backtraces.xml (In reply to comment #2) > Reading symbols from /usr/bin/fwbuilder...(no debugging symbols found)...done. > > also, there is no /usr/lib/debug directory Try adding "installsources" to FEATURES for the build, but also install dev-util/debugedit first (it is required for installsources, and it may be an undocumented requirement for splitdebug -- I normally use them together) Bug 372203 is the reason why you cannot get any debug info, I'd guess. Let's fix that first... Please re-sync your portage tree in two hours or so and then try again... then you should get the debug information. Is this still an issue in 5.0.0.3568 and the soon-to-be-in-the-tree 5.0.1.3592? (In reply to comment #7) > Is this still an issue in 5.0.0.3568 and the soon-to-be-in-the-tree 5.0.1.3592? Well, I thought I could test it. Unfortunately fwbuilder des not want to live: ../fwbuilder/uint128.h:469:29: error: expected ')' before 'PRIX64' ../fwbuilder/uint128.h:469:93: warning: spurious trailing '%' in format ../fwbuilder/uint128.h:469:93: warning: too many arguments for format ../fwbuilder/uint128.h:471:28: error: expected ')' before 'PRIX64' ../fwbuilder/uint128.h:471:57: warning: spurious trailing '%' in format ../fwbuilder/uint128.h:471:57: warning: too many arguments for format In file included from ../fwbuilder/InetAddr.h:49:0, from ../fwbuilder/Address.h:31, from ../fwbuilder/Host.h:33, from ../fwbuilder/Firewall.h:30, from Firewall.cpp:36: ../fwbuilder/uint128.h: In member function 'std::string uint128::to_string() const': ../fwbuilder/uint128.h:469:29: error: expected ')' before 'PRIX64' ../fwbuilder/uint128.h:469:93: warning: spurious trailing '%' in format ../fwbuilder/uint128.h:469:93: warning: too many arguments for format ../fwbuilder/uint128.h:471:28: error: expected ')' before 'PRIX64' ../fwbuilder/uint128.h:471:57: warning: spurious trailing '%' in format ../fwbuilder/uint128.h:471:57: warning: too many arguments for format distcc[26314] ERROR: compile (null) on localhost failed distcc[26248] ERROR: compile Cluster.cpp on localhost failed make[4]: *** [.obj/Cluster.o] Error 1 distcc[26310] ERROR: compile (null) on localhost failed distcc[26246] ERROR: compile Firewall.cpp on localhost failed make[4]: *** [.obj/Firewall.o] Error 1 make[4]: Leaving directory `/var/tmp/portage/net-firewall/fwbuilder-5.0.0.3568/work/fwbuilder-5.0.0.3568/src/libfwbuilder/src/fwbuilder' make[3]: *** [sub-fwbuilder-make_default-ordered] Error 2 make[3]: Leaving directory `/var/tmp/portage/net-firewall/fwbuilder-5.0.0.3568/work/fwbuilder-5.0.0.3568/src/libfwbuilder/src' make[2]: *** [sub-src-make_default] Error 2 make[2]: Leaving directory `/var/tmp/portage/net-firewall/fwbuilder-5.0.0.3568/work/fwbuilder-5.0.0.3568/src/libfwbuilder' make[1]: *** [sub-libfwbuilder-make_default-ordered] Error 2 make[1]: Leaving directory `/var/tmp/portage/net-firewall/fwbuilder-5.0.0.3568/work/fwbuilder-5.0.0.3568/src' make: *** [sub-src-make_default] Error 2 * ERROR: net-firewall/fwbuilder-5.0.0.3568 failed (compile phase): * emake failed (In reply to comment #8) > (In reply to comment #7) > > Is this still an issue in 5.0.0.3568 and the soon-to-be-in-the-tree 5.0.1.3592? > > > Well, I thought I could test it. Unfortunately fwbuilder des not want to live: > [...] Made a separate bug for that... ... and unfortunately we can't debug a segfault without a backtrace... |