receiving signal SIGSEGV, Segmentation fault when running a node

asked 2018-09-15 05:30:34 -0500

jafar_abdi
221 ●7 ●13 ●18

updated 2018-09-15 05:33:42 -0500

Hello everyone,

I getting "Segmentation fault (core dumped)" error when running a node, despite the fact that it worked well before

when I run it with gdb I'm getting this

Starting program: /home/jafar/catkin_ws/devel/lib/kuka_arm/trajectory_sampler 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffd8257700 (LWP 3192)]
[New Thread 0x7fffd7a56700 (LWP 3193)]
[New Thread 0x7fffd7255700 (LWP 3194)]
[New Thread 0x7fffd6a54700 (LWP 3199)]
[New Thread 0x7fffd6253700 (LWP 3200)]
[New Thread 0x7fffd5a52700 (LWP 3213)]

Thread 1 "trajectory_samp" received signal SIGSEGV, Segmentation fault.
0x00007ffff55d8f18 in ros::WallTime::now() ()
from /opt/ros/kinetic/lib/librostime.so

Anyone know why this's happening ..?

Thanks

edit retag flag offensive close merge delete

add a comment

3

answered 2018-09-15 13:03:41 -0500

gvdhoorn
86574 ●283 ●1432 ●1054 http://cor.tudelft.nl/

updated 2018-09-16 03:09:50 -0500

There have been a nr of reports of ABI breakages with Kinetic after the last sync.

Have you rebuilt your workspace recently and/or upgraded all packages?

edit flag offensive delete link

Comments

1

It worked after I run

sudo apt-get update
sudo apt-get upgrade

jafar_abdi ( 2018-09-15 14:43:20 -0500 )edit

add a comment

0

answered 2019-01-13 22:14:55 -0500

hungpham
1

It is not necessary to upgrade all libraries. In my case, upgrading ros-kinetic related package does it.

sudo apt update
sudo apt install --only-upgrade ros-kinetic-*

edit flag offensive delete link

Comments

1

That is true, but I would at least upgrade all ROS packages together. There is as of now no ABI bw compatibility guarantee for any of the ROS 1 (and ROS 2) packages, so performing partial upgrades you'll always run the risk of more ABI problems.

gvdhoorn ( 2019-01-14 02:16:31 -0500 )edit

add a comment

receiving signal SIGSEGV, Segmentation fault when running a node

2 Answers

Comments

Comments

Question Tools

Stats

Related questions

receiving signal SIGSEGV, Segmentation fault when running a node edit

2 Answers

Comments

Comments

Question Tools

Stats

Related questions

receiving signal SIGSEGV, Segmentation fault when running a node