from /var/tmp/portage/dev-ros/imu_processors-0.3.0/work/imu_pipeline-0.3.0/imu_processors/src/imu_bias_remover.cpp:34: /usr/include/ros/subscription_callback_helper.h: In member function ‘ros::VoidConstPtr ros::SubscriptionCallbackHelperT<P, Enabled>::deserialize(const ros::SubscriptionCallbackHelperDeserializeParams&) [with P = const boost::shared_ptr<const geometry_msgs::Twist_<std::allocator<void> > >&; Enabled = void]’: /usr/include/ros/subscription_callback_helper.h:118:24: internal compiler error: Segmentation fault 118 | virtual VoidConstPtr deserialize(const SubscriptionCallbackHelperDeserializeParams& params) | ^~~~~~~~~~~ 0xcd63af crash_signal /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/toplev.c:327 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no-multilib-20210423-202814 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-10.3.0 [3] x86_64-pc-linux-gnu-11.1.0 * clang version 12.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/12/bin /usr/lib/llvm/12 12.0.0 Python 3.8.9 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby30 (with Rubygems) * Available Rust versions: [1] rust-bin-1.51.0 * The Glorious Glasgow Haskell Compilation System, version 8.10.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Wed Apr 28 04:35:22 UTC 2021 emerge -qpvO dev-ros/imu_processors [ebuild N ] dev-ros/imu_processors-0.3.0 USE="-test" PYTHON_SINGLE_TARGET="python3_8 -python3_7"
Created attachment 703020 [details] emerge-info.txt
Created attachment 703023 [details] dev-ros:imu_processors-0.3.0:20210428-050638.log
Created attachment 703026 [details] emerge-history.txt
Created attachment 703029 [details] environment
Created attachment 703032 [details] etc.portage.tar.bz2
Created attachment 703035 [details] logs.tar.bz2
Created attachment 703038 [details] temp.tar.bz2
""" FAILED: CMakeFiles/imu_bias_remover.dir/src/imu_bias_remover.cpp.o /usr/bin/x86_64-pc-linux-gnu-g++ -DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 -DROS_PACKAGE_NAME=\"imu_processors\" -I/usr/share/xmlrpcpp/cmake/../../../include/xmlrpcpp -pipe -march=native -fno-diagnostics-color -Og -g -std=c++14 -MD -MT CMakeFiles/imu_bias_remover.dir/src/imu_bias_remover.cpp.o -MF CMakeFiles/imu_bias_remover.dir/src/imu_bias_remover.cpp.o.d -o CMakeFiles/imu_bias_remover.dir/src/imu_bias_remover.cpp.o -c /var/tmp/portage/dev-ros/imu_processors-0.3.0/work/imu_pipeline-0.3.0/imu_processors/src/imu_bias_remover.cpp In file included from /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22, from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23, from /usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14, from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42, from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25, from /usr/include/boost/smart_ptr/shared_ptr.hpp:29, from /usr/include/boost/shared_ptr.hpp:17, from /usr/include/ros/forwards.h:37, from /usr/include/ros/common.h:37, from /usr/include/ros/ros.h:43, from /var/tmp/portage/dev-ros/imu_processors-0.3.0/work/imu_pipeline-0.3.0/imu_processors/src/imu_bias_remover.cpp:34: /usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’ 36 | BOOST_PRAGMA_MESSAGE( | ^~~~~~~~~~~~~~~~~~~~ during GIMPLE pass: strlen In file included from /usr/include/ros/subscriber.h:33, from /usr/include/ros/node_handle.h:33, from /usr/include/ros/ros.h:45, from /var/tmp/portage/dev-ros/imu_processors-0.3.0/work/imu_pipeline-0.3.0/imu_processors/src/imu_bias_remover.cpp:34: /usr/include/ros/subscription_callback_helper.h: In member function ‘ros::VoidConstPtr ros::SubscriptionCallbackHelperT<P, Enabled>::deserialize(const ros::SubscriptionCallbackHelperDeserializeParams&) [with P = const boost::shared_ptr<const geometry_msgs::Twist_<std::allocator<void> > >&; Enabled = void]’: /usr/include/ros/subscription_callback_helper.h:118:24: internal compiler error: Segmentation fault 118 | virtual VoidConstPtr deserialize(const SubscriptionCallbackHelperDeserializeParams& params) | ^~~~~~~~~~~ 0xcd63af crash_signal /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/toplev.c:327 0x7eff3a18866f ??? /var/tmp/portage/sys-libs/glibc-2.33/work/glibc-2.33/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0 0x174c60d cpp_interpret_string_1 /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/libcpp/charset.c:1667 0x174cd4e cpp_interpret_string_ranges(cpp_reader*, cpp_string const*, cpp_string_location_reader*, unsigned long, cpp_substring_ranges*, cpp_ttype) /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/libcpp/charset.c:1850 0x174671a get_substring_ranges_for_loc /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/input.c:1510 0x174671a get_location_within_string(cpp_reader*, string_concat_db*, unsigned int, cpp_ttype, int, int, int, unsigned int*) /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/input.c:1555 0x8158fb c_get_substring_location(substring_loc const&, unsigned int*) /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/c-family/c-common.c:914 0xcd0a17 substring_loc::get_location(unsigned int*) const /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/substring-locations.c:284 0xcd0a17 format_string_diagnostic_t::emit_warning_n_va(int, unsigned long, char const*, char const*, __va_list_tag (*) [1]) const /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/substring-locations.c:156 0x1602284 fmtwarn /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/gimple-ssa-sprintf.c:339 0x1602be4 maybe_warn /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/gimple-ssa-sprintf.c:2985 0x16067b5 format_directive /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/gimple-ssa-sprintf.c:3141 0x16067b5 compute_format_length /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/gimple-ssa-sprintf.c:4009 0x16067b5 handle_printf_call(gimple_stmt_iterator*, pointer_query&) /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/gimple-ssa-sprintf.c:4682 0xe74770 strlen_check_and_optimize_call /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/tree-ssa-strlen.c:5205 0xe74770 check_and_optimize_stmt /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/tree-ssa-strlen.c:5373 0xe74770 strlen_dom_walker::before_dom_children(basic_block_def*) /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/tree-ssa-strlen.c:5625 0x15b2eb7 dom_walker::walk(basic_block_def*) /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/domwalk.c:309 0xe6cde6 printf_strlen_execute /var/tmp/portage/sys-devel/gcc-11.1.0/work/gcc-11.1.0/gcc/tree-ssa-strlen.c:5691 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://bugs.gentoo.org/> for instructions. """ That looks like a compiler bug. Unless it's an OOM (dmesg should complain about it). If you can still reproduce it can you expand -march=native and extract preprocessed file following https://wiki.gentoo.org/wiki/Gcc-ICE-reporting-guide ?
emerged fine the 2nd time - found no OOM in the host syslog - hhm ?
It looks like the gcc crashed in a very simple piece of code. My worry is that it's a memory corruption caused by hardware failure or unrelated software failure (like a kernel bug). I wonder if you could run a memtest on that machine to see if it looks fine.
(In reply to Sergei Trofimovich from comment #10) > It looks like the gcc crashed in a very simple piece of code. > > My worry is that it's a memory corruption caused by hardware failure or > unrelated software failure (like a kernel bug). > > I wonder if you could run a memtest on that machine to see if it looks fine. (In reply to Toralf Förster from comment #9) > emerged fine the 2nd time - found no OOM in the host syslog - hhm ? maybe, but there's nothing ros@ can do about this I'm afraid
*** This bug has been marked as a duplicate of bug 828872 ***
