Gazebo | Ignition | Community
Ask Your Question

[ROS1][Gazebo-2] Segfault for exit code 139

asked 2020-04-06 09:36:39 -0500

acbuynak gravatar image

Hello! I am attempting to simulate my robot in Gazebo9 with ROS.

I was able to get everything working on a VM, but when setting up a dedicated Linux Box using the same setup I am running into this error. To ensure the same 'setup' I have created a bash shell script for the install of ros, gazebo, needed packages.

Primary Issue: Exit Code 139.. No log file was created.

_OS: Ubuntu 18.04.4 LTS Bionic Beaver
_Memory: 3.8 GiB
_Processor: Intel Core 2 Duo E7300

Output from roslaunch:
(excluded roscore opening)

setting /run_id to d40f25f8-780d-11ea-997a-00219b197d0c
process[rosout-1]: started with pid [4974]
started core service [/rosout]
process[gazebo-2]: started with pid [4977]
process[gazebo_gui-3]: started with pid [4979]
process[urdf_spawner-4]: started with pid [4987]
[INFO] [1586181165.841650, 0.000000]: Loading model XML from ros parameter robot_description
[INFO] [1586181165.854874, 0.000000]: Waiting for service /gazebo/spawn_urdf_model
[ INFO] [1586181166.975886346]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1586181166.976646368]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1586181166.981193263]: waitForService: Service [/gazebo_gui/set_physics_properties] has not been advertised, waiting...
[ INFO] [1586181166.998543667]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...

Error Statement:

Segmentation fault (core dumped)
[gazebo-2] process has died [pid 4977, exit code 139, cmd /opt/ros/melodic/lib/gazebo_ros/gzserver -e ode /home/a/ws_core/src/gazebo_world/worlds/ __name:=gazebo __log:=/home/a/.ros/log/d40f25f8-780d-11ea-997a-00219b197d0c/gazebo-2.log].
log file: /home/a/.ros/log/d40f25f8-780d-11ea-997a-00219b197d0c/gazebo-2*.log
Segmentation fault (core dumped)
[gazebo_gui-3] process has died [pid 4979, exit code 139, cmd /opt/ros/melodic/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/a/.ros/log/d40f25f8-780d-11ea-997a-00219b197d0c/gazebo_gui-3.log].
log file: /home/a/.ros/log/d40f25f8-780d-11ea-997a-00219b197d0c/gazebo_gui-3*.log

Related Errors
I was unable to determine if this question was related.

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2023-01-24 02:40:57 -0500

if you are running MAVROS this may be helpful

DONT_RUN=1 make px4_sitl_default gazebo
source ~/catkin_ws/devel/setup.bash    # (optional)
source Tools/simulation/gazebo/setup_gazebo.bash $(pwd) $(pwd)/build/px4_sitl_default
export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:$(pwd)/Tools/simulation/gazebo/sitl_gazebo
roslaunch px4 posix_sitl.launch

edit flag offensive delete link more

answered 2020-04-06 13:08:35 -0500

acbuynak gravatar image

I was unable to determine the root cause of this error statement.

I was able to resolve my issue through checking and taking a few steps. If you are attempting to troubleshoot, I would suggest these steps.

Ensure Gazebo works in Standalone.
..Have you checked if you need to turn off hardware acceleration?

Is your environment setup properly? Sourced?
..Manually source your 'build' in each terminal.

Ensure Gazebo ROS & Gazebo ROS Control Packages are Installed

sudo apt-get install -y ros-melodic-gazebo-ros
sudo apt-get install -y ros-melodic-gazebo-ros-pkgs ros-melodic-gazebo-ros-control

Ensure the appropriate PID controller package is installed

sudo apt-get install -y ros-melodic-position-controllers
sudo apt-get install -y ros-melodic-effort-controllers
sudo apt-get install -y ros-melodic-joint-state-controller

Ensure your robot description and controllers are in the same namespace.
..I utilized a Xacro and have a <xacro robot: NAME> and a controller initializer that separately 'name' the robot. These needed to be the same (obvs) to function.

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2020-04-06 09:36:39 -0500

Seen: 6,258 times

Last updated: Apr 06 '20