roslaunch: [gazebo-2] process has died [pid 7605, exit code 139
After running my model with roslaunch for round about 10 to 20 minutes I always get the following error:
Segmentation fault (core dumped)
[gazebo-2] process has died [pid 7605, exit code 139, cmd /opt/ros/kinetic/lib/gazebo_ros/gzserver -e ode /home/philipp/navibot_ws/src/navibot_gazebo/worlds/navibot.world __name:=gazebo __log:=/home/philipp/.ros/log/09e16ec0-4a76-11e7-a9fe-7085c23141c2/gazebo-2.log].
log file: /home/philipp/.ros/log/09e16ec0-4a76-11e7-a9fe-7085c23141c2/gazebo-2*.log
Unfortunately no log file gazebo-2*.log
is created.
I looked through my URDF model and checked my code. The problem is that I have a hard time to identify where the problem is really coming from, so I am looking for help here. I looked at the related questions here in the forum, but none of the solutions there worked for me.
This is my backtrace:
Thread 25 "gzserver" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff67fff700 (LWP 28488)]
gazebo::physics::World::Update (this=this@entry=0x12075a0) at /build/gazebo-nhSAPd/g
740 /build/gazebo-nhSAPd/gazebo-7.0.0+dfsg/gazebo/physics/World.cc: No such file
(gdb) backtrace
0 gazebo::physics::World::Update (this=this@entry=0x12075a0) at /build/gazebo-nhSA
1 0x00007ffff62d99af in gazebo::physics::World::Step (this=this@entry=0x12075a0) a
2 0x00007ffff62d9e25 in gazebo::physics::World::RunLoop (this=0x12075a0) at /build
3 0x00007ffff40d95d5 in ?? () from /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.
4 0x00007ffff65ee6ba in start_thread (arg=0x7fff67fff700) at pthread_create.c:333
5 0x00007ffff6bef82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
(gdb) frame 0
0 gazebo::physics::World::Update (this=this@entry=0x12075a0) at /build/gazebo-nhSAPd/gazebo-7.0.0+dfsg/gazebo /physics/World.cc:740
740 in /build/gazebo-nhSAPd/gazebo-7.0.0+dfsg/gazebo/physics/World.cc
(gdb) frame 1
1 0x00007ffff62d99af in gazebo::physics::World::Step (this=this@entry=0x12075a0) at /build/gazebo-nhSAPd/gazebo-7.0.0+dfsg/gazebo/physics/World.cc:672
672 in /build/gazebo-nhSAPd/gazebo-7.0.0+dfsg/gazebo/physics/World.cc
(gdb) frame 2
2 0x00007ffff62d9e25 in gazebo::physics::World::RunLoop (this=0x12075a0) at /build/gazebo-nhSAPd/gazebo- 7.0.0+dfsg/gazebo/physics/World.cc:481
481 in /build/gazebo-nhSAPd/gazebo-7.0.0+dfsg/gazebo/physics/World.cc
(gdb) frame 3
3 0x00007ffff40d95d5 in ?? () from /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.58.0
(gdb) frame 4
4 0x00007ffff65ee6ba in start_thread (arg=0x7fff67fff700) at pthread_create.c:333
333 pthread_create.c: No such file or directory.
(gdb) frame 5
5 0x00007ffff6bef82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
109 ../sysdeps/unix/sysv/linux/x86_64/clone.S: No such file or directory.
Asked by Kaonashi on 2017-06-06 00:26:24 UTC
Comments
From your backtrace this would seem to be an internal problem of Gazebo -- possible aggrevated / exposed by usage through ROS. I would really recommend that you try and post your question over at
answers.gazebosim.org
, as that is where Gazebo is supported. We're just users, as you are.Asked by gvdhoorn on 2017-06-07 00:52:15 UTC
I'm going to close this one, but could I ask you to post a link to your post on
answers.gazebosim.org
if/when you do post there? That way we can keep things connected.Asked by gvdhoorn on 2017-06-07 00:53:16 UTC
Thanks for your reply and sorry for posting it at the wrong place. Here is the link to
answers.gazeboism.org
Asked by Kaonashi on 2017-06-07 01:10:54 UTC
No problem. It gets confusing with all the different support and discussion fora. I just wanted to increase your chances of gettnig a good answer, as the ppl over at the Gazebo Q&A are experts: it's their software after all. I'd also consider submitting a bug report.
Asked by gvdhoorn on 2017-06-07 01:13:50 UTC