Revision history [back]

There are some (probably) related questions over at answers.gazebosim.org (searching for gazebo exit code 139) and I also believe that ros-simulation/gazebo_ros_pkgs#387 is related.

There are some (probably) related questions over at answers.gazebosim.org (searching for gazebo exit code 139) and I also believe that ros-simulation/gazebo_ros_pkgs#387 is related.

There are some (probably) related questions over at answers.gazebosim.org (searching for gazebo exit code 139) and I also believe that ros-simulation/gazebo_ros_pkgs#387 is related.

Does the ROS development community have the same view on this?

As much as I appreciate humor, doing it this way might not be conducive to you getting answers quicker on this forum.

Yes, SEGFAULTs are obviously considered problematic (and I don't think you and your bosses are alone in that), so they should be reported.

How to figure out why?

I would try and start gzserver directly, not from a launch file. If it still crashes, #387 is probably not related. If it doesn't, it probably is.

Next question are Where/how to report [..]

Gazebo is slightly special, in that it is a stand-alone tool, but has a tight ROS integration available. As this is the crash seems to point to gazebo_ros, it's probably a good idea to first check ros-simulation/gazebo_ros_pkgs/issues. If it turns out to be on the Gazebo related, side, then I would try the Gazebo answers site, the troubleshooting page and finally if it does turn out to be an unknown bug, the issue tracker.

There are some (probably) related questions over at answers.gazebosim.org (searching for gazebo exit code 139) and I also believe that ros-simulation/gazebo_ros_pkgs#387 is related.

Does the ROS development community have the same view on this?

As much as I appreciate humor, doing it this way might not be conducive to you getting answers quicker on this forum.

Yes, SEGFAULTs are obviously considered problematic (and I don't think you and your bosses are alone in that), so they should be reported.

How to figure out why?

I would try and start gzserver directly, not from a launch file. If it still crashes, #387 is probably not related. If it doesn't, it probably is.

Next question are Where/how to report [..]

Gazebo is slightly special, in that it is a stand-alone tool, but has a tight ROS integration available. As the crash seems to point to gazebo_ros, it's probably a good idea to first check ros-simulation/gazebo_ros_pkgs/issues. If it turns out to be on the Gazebo side, then I would try the Gazebo answers site, the troubleshooting page and finally if it does turn out to be an unknown bug, the issue tracker.

There are some (probably) related questions over at answers.gazebosim.org (searching for gazebo exit code 139) and I also believe that ros-simulation/gazebo_ros_pkgs#387 is related.

Does the ROS development community have the same view on this?

As much as I appreciate humor, doing it this way might not be conducive to you getting answers quicker on this forum.

Yes, SEGFAULTs are obviously considered problematic (and I (I don't think you and your bosses are alone in that), so they should be reported.

How to figure out why?

I would try and start gzserver directly, not from a launch file. If it still crashes, #387 is probably not related. If it doesn't, it probably is.

Next question are Where/how to report [..]

Gazebo is slightly special, in that it is a stand-alone tool, but has a tight ROS integration available. As the crash seems to point to gazebo_ros, it's probably a good idea to first check ros-simulation/gazebo_ros_pkgs/issues. If it turns out to be on the Gazebo side, then I would try the Gazebo answers site, the troubleshooting page and finally if it does turn out to be an unknown bug, the issue tracker.

See the Support guidelines on the wiki for more information.

There are some (probably) related questions over at answers.gazebosim.org (searching for gazebo exit code 139) and I also believe that ros-simulation/gazebo_ros_pkgs#387 is related.

Does the ROS development community have the same view on this?

As much as I appreciate humor, doing it this way might not be conducive to you getting answers quicker on this forum.

Yes, SEGFAULTs are obviously considered problematic (I don't think you and your bosses are alone in that), so they should be reported.

How to figure out why?

I would try and start gzserver directly, not from a launch file. If it still crashes, #387 is probably not related. If it doesn't, it probably is.

Next question are Where/how to report [..]

Gazebo is slightly special, in that it is a stand-alone tool, but has a tight ROS integration available. As the crash seems to point to gazebo_ros, it's probably a good idea to first check ros-simulation/gazebo_ros_pkgs/issues. If it turns out to be on the Gazebo side, then I would try the Gazebo answers site, the troubleshooting page and finally if it does turn out to be an unknown bug, the issue tracker.

See the Support guidelines on the wiki for more information.