Gazebo simulator crashes when deleting model
I have a model which is pretty complex:
- 9 links
- 8 joints
- 3 plugins
The problem is that when I right click the name of the model in the World section of Gazebo simulator and delete the object, I get the following error.
terminate called without an active exception
Aborted (core dumped)
[gazebo-2] process has died [pid 4248, exit code 134, cmd /opt/ros/melodic/lib/gazebo_ros/gzserver -u -e ode /home/USER/Documents/WORKSPACE/src/PKG/worlds/world.world __name:=gazebo __log:=/home/USER/.ros/log/fb1083ce-306b-11eb-917e-080027837983/gazebo-2.log].
log file: /home/USER/.ros/log/fb1083ce-306b-11eb-917e-080027837983/gazebo-2*.log
As @nlamprian stated, I tried with debug and I got this message:
Thread 42 "gzserver" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fff2dfa5700 (LWP 31605)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb)
Run gazebo with the debug flag to true and check the stacktrace after the crash to see at which point (in which plugin probably) gazebo crashed
how exactly should I do this? The debug flag is related to the node launched by roslaunch? Or is a Gazeboo setting? Thanks for the prompt answer
You need to set the argument wherever you include this launch file.
with debugging mode on the error doesn't show up when I add or remove multiple instances of the object which used to generate the errors without debug mode on. What next? P.s thanks for the solution it is a good alternative to let the debugging mode on ? or it adds delays to my program
I got one error while debugging mode was on - what should I do now?