mlanting's profile - activity

have you tried running the launch command with the -d option for more debug output?

You could look at the demos repository. The composition and lifecycle packages use launch files. https://github.com/ros2

I don't see anything obvious that's wrong. Did you remember to run colcon build and re-source the workspace?

You could look through the git history of the tutorial on github if you need to refer to an older version: https://githu

Exactly what I needed, thanks!

Is there a way to get Colcon to build ROS2 binaries with debug symbols so that I can run nodes with something like DDD?

I'm able to run using DDD with the following command:

ros2 run --prefix 'ddd' ros1_bridge dynamic_bridge

But without debug symbols, I can't use feature like breakpoints or stepping through the source code.

ROS2 Colcon debug symbols for use with DDD Is there a way to get Colcon to build ROS2 binaries with debug symbols so tha

I use vim, but when I want the features of an IDE like Eclipse, I use Eclim ( http://eclim.org/ ) to access a headless instance of Eclipse fairly seamlessly right from vim. The biggest things are that when Eclipse has an issues it's even less graceful about it than when you're using the GUI, and that I sometimes futz around a bit when I pull in a new dependency to get it recognized properly. Maybe that's an issue with the GUI Eclipse too, but I haven't used Eclipse "normally" in a while.

People have also made plugins to support using Eclim with other popular editors as well.

what do you do about generated source files that end up in the src directory? Do you just let them be, or add something like src/my_package to svn ignore?

I have not used Vicon at all, but I am getting the same kind of error with a node I made for the Bumblebee2 stereo camera. I wanted to use the Triclops library for stereo processing which did not play well with ROS, but I managed to get it working on my previous setup (Electric + Lucid). The problem then was a Boost incompatibility between the Point Grey Triclops library and ROS which I was able to work around by limiting the Triclops library to one thread with a parameter.

After upgrading to Fuerte and Precise I get the same malloc error (more or less..) when starting the node. Where before the problem was a segfault during stereo processing, I now have it happening during camera initialization which uses a wrapper library from Point Grey for libdc1394 which I got to work with the libdc1394v2 ROS package.

I have not yet made a lot of progress in solving the issue, but I suspect a Boost incompatibility again (only seemingly more severe...). I'm not sure yet if the problem is with libdc1394v2 or the Triclops wrapper. I will update if/when I learn more about the problem. Sorry this isn't really an answer (yet), but it wouldn't fit as a comment...

I've tried both of those. Trying a package (I only tried the first ones) gives a message just telling me the package is broken.

edited to include error output.

I am trying to re-install ROS, and deleted the old install (which was Electric). I followed the instructions for installing Fuerte, and get a series of "Unmet dependencies" errors saying the packages are broken. I then tried installing electric again, and get the same error with the same list of broken packages (only with electric in the name instead of fuerte). Any idea what could be causing this?

EDIT: more information on the error: Linux version is Ubuntu 10.04

$ sudo apt-get install ros-fuerte-desktop-full

Reading package lists... Done
Building dependency tree Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
 
The following packages have unmet dependencies:
  ros-fuerte-desktop-full: Depends: ros-fuerte-geometry-tutorials (= 0.1.3-s1336                                                                                   651950~lucid) but it is not going to be installed
                           Depends: ros-fuerte-orocos-kinematics-dynamics (= 0.2                                                                                   .3-s1336639670~lucid) but it is not going to be installed
                           Depends: ros-fuerte-slam-gmapping (= 1.2.7-s133667560                                                                                   2~lucid) but it is not going to be installed
                           Depends: ros-fuerte-simulator-gazebo (= 1.6.7-s133665                                                                                   4046~lucid) but it is not going to be installed
                           Depends: ros-fuerte-visualization (= 1.8.11-s13366454                                                                                   67~lucid) but it is not going to be installed
                           Depends: ros-fuerte-vision-opencv (= 1.8.2-s133664006                                                                                   6~lucid) but it is not going to be installed
                           Depends: ros-fuerte-perception-pcl (= 1.2.2-s13366407                                                                                   65~lucid) but it is not going to be installed
                           Depends: ros-fuerte-geometry-experimental (= 0.2.3-s1                                                                                   336647863~lucid) but it is not going to be installed
                           Depends: ros-fuerte-common-tutorials (= 0.2.3-s133665                                                                                   2686~lucid) but it is not going to be installed
                           Depends: ros-fuerte-image-pipeline (= 1.8.2-s13366410                                                                                   90~lucid) but it is not going to be installed
                           Depends: ros-fuerte-geometry-visualization (= 0.1.1-s                                                                                   1336660261~lucid) but it is not going to be installed
                           Depends: ros-fuerte-stage (= 1.6.6-s1336651803~lucid)                                                                                    but it is not going to be installed
                           Depends: ros-fuerte-image-transport-plugins (= 1.8.0-                                                                                   s1336640188~lucid) but it is not going to be installed
                           Depends: ros-fuerte-robot-model (= 1.8.0-s1336641692~                                                                                   lucid) but it is not going to be installed
                           Depends: ros-fuerte-geometry (= 1.8.0-s1336639813~luc                                                                                   id) but it is not going to be installed
                           Depends: ros-fuerte-visualization-tutorials (= 0.6.3-                                                                                   s1336660788~lucid) but it is not going to be installed
                           Depends: ros-fuerte-laser-pipeline (= 1.4.4-s13366436                                                                                   35~lucid) but it is not going to be installed
                           Depends: ros-fuerte-navigation (= 1.8.1-s1336674623~l                                                                                   ucid) but it is not going to be installed
E: Broken packages
 

I've been having this same problem. The quickest and easiest fix I've found so far is just to call triclopsSetMaxThreadCount and set it to 1. It hasn't segfaulted since I tried that, though it's not performing as well.