Ask Your Question
0

ROS system randomly crashes and gdb says corrupt stack in callback queue

asked 2016-04-05 20:41:23 -0600

Sebastian gravatar image

My ROS system randomly crashes and I decided to run gdb at all times to catch it next time it happens.

I caught it and this is the output from gdb:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x6deff420 (LWP 25232)]
0x0003d210 in boost::detail::sp_counted_base::release() ()
(gdb) bt
#0  0x0003d210 in boost::detail::sp_counted_base::release() ()
#1  0x76409570 in ros::SubscriptionQueue::call() () from /opt/ros/indigo/lib/libroscpp.so
#2  0x763baa84 in ros::CallbackQueue::callOneCB(ros::CallbackQueue::TLS*) () from /opt/ros/indigo/lib/libroscpp.so
#3  0x6defec5c in ?? ()
#4  0x6defec5c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Obviously that is not much help! Does anyone have an idea how I can go about debugging this? Point me in the right direction? Thanks

edit retag flag offensive close merge delete

Comments

I face the same error here. Any solution?

mrrius gravatar imagemrrius ( 2019-11-20 00:18:42 -0600 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2016-04-05 21:55:22 -0600

ahendrix gravatar image

Looks like stack corruption. I'd start by running your node in valgrind, and if that doesn't find anything I'd start looking for more specific tools for debugging stack overruns.

edit flag offensive delete link more

Comments

Thanks. I had heard of valgrind but I've never used it before. I'll give it a look.

Sebastian gravatar imageSebastian ( 2016-04-05 23:14:56 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2016-04-05 20:41:23 -0600

Seen: 112 times

Last updated: Apr 05 '16