Hi Dino, * H. <work@hllmnn.de> [2018-09-20 09:45]:
To investigate the problem, I took the source of rosconsole from https://github.com/ros/rosconsole (as well as roscpp), compiled it and linked against it. The problem was gone, so I think this issue is caused by wrong linkage to log4cxx in Testing.
Thanks a lot for the report, I was able to reproduce this on my computer and filled a binNMU request here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909273This means the package will be rebebuild and the error should be gone soon.
But even after rebuilding ros-rosconsole and ros-ros-comm (roscpp), valgring complains about uninitialised values (log below). I have no idea where this is coming from but didn't look very deep. Where your rebuilds valgrind clean?
Btw. While mails are fine, you could use reportbug <package> to report bugs in Debian and to track them properly.
Cheers Jochen ==22669== Memcheck, a memory error detector ==22669== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==22669== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==22669== Command: ./t ==22669== [ INFO] [1537471322.804086582]: Hello World ==22669== Conditional jump or move depends on uninitialised value(s) ==22669== at 0x49B80BF: ros::ROSOutAppender::log(ros::console::levels::Level, char const*, char const*, char const*, int) (in /usr/lib/x86_64-linux-gnu/libroscpp.so.1.14.2) ==22669== by 0x4AF3040: ros::console::impl::Log4cxxAppender::append(log4cxx::helpers::ObjectPtrT<log4cxx::spi::LoggingEvent> const&, log4cxx::helpers::Pool&) (in /usr/lib/x86_64-linux-gnu/librosconsole_log4cxx.so.1.13.7) ==22669== by 0x4BEDA18: log4cxx::AppenderSkeleton::doAppend(log4cxx::helpers::ObjectPtrT<log4cxx::spi::LoggingEvent> const&, log4cxx::helpers::Pool&) (in /usr/lib/x86_64-linux-gnu/liblog4cxx.so.10.0.0) ==22669== by 0x4BEBC33: log4cxx::helpers::AppenderAttachableImpl::appendLoopOnAppenders(log4cxx::helpers::ObjectPtrT<log4cxx::spi::LoggingEvent> const&, log4cxx::helpers::Pool&) (in /usr/lib/x86_64-linux-gnu/liblog4cxx.so.10.0.0) ==22669== by 0x4C29D5C: log4cxx::Logger::callAppenders(log4cxx::helpers::ObjectPtrT<log4cxx::spi::LoggingEvent> const&, log4cxx::helpers::Pool&) const (in /usr/lib/x86_64-linux-gnu/liblog4cxx.so.10.0.0) ==22669== by 0x4C29F8D: log4cxx::Logger::forcedLog(log4cxx::helpers::ObjectPtrT<log4cxx::Level> const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, log4cxx::spi::LocationInfo const&) const (in /usr/lib/x86_64-linux-gnu/liblog4cxx.so.10.0.0) ==22669== by 0x4AF0166: ros::console::impl::print(void*, ros::console::levels::Level, char const*, char const*, char const*, int) (in /usr/lib/x86_64-linux-gnu/librosconsole_log4cxx.so.1.13.7) ==22669== by 0x4AC701D: ros::console::print(ros::console::FilterBase*, void*, ros::console::levels::Level, char const*, int, char const*, char const*, ...) (in /usr/lib/x86_64-linux-gnu/librosconsole.so.1.13.7) ==22669== by 0x10A43E: main (in /home/jspricke/t) ==22669== ==22669== ==22669== HEAP SUMMARY: ==22669== in use at exit: 4,516 bytes in 50 blocks ==22669== total heap usage: 1,387 allocs, 1,337 frees, 236,561 bytes allocated ==22669== ==22669== LEAK SUMMARY: ==22669== definitely lost: 0 bytes in 0 blocks ==22669== indirectly lost: 0 bytes in 0 blocks ==22669== possibly lost: 304 bytes in 1 blocks ==22669== still reachable: 4,212 bytes in 49 blocks ==22669== suppressed: 0 bytes in 0 blocks ==22669== Rerun with --leak-check=full to see details of leaked memory ==22669== ==22669== For counts of detected and suppressed errors, rerun with: -v ==22669== Use --track-origins=yes to see where uninitialised values come from ==22669== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Attachment:
signature.asc
Description: PGP signature