Re: [ROS] librosconsole defective?
Hi Jochen,
Thanks for triggering the rebuild process! The hint about the reportbug
command is also good, I will use that in the future. Thanks :)
I investigated the code valgrind was still complaining about and pushed
a fix: https://github.com/ros/ros_comm/pull/1507
It seems as if a parameter called rosout_disable_topics_generation was
introduced recently in ROS, which is undefined in the Debian packages.
I have no idea which mechanism is setting such parameters, I only know
about roslaunch. However, I'm just happy with the default value...
Best,
Dino
On 20.09.2018, 21:29 +0200 Jochen Sprickerhof wrote:
> 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=909273
>
> This 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
>
Reply to: