Ask Your Question
1

Openni_tracker crashes with a segmentation fault (core dumped). [closed]

asked 2013-06-12 03:32:22 -0500

updated 2013-06-12 22:29:37 -0500

Any idea on what is causing it ? It is running on Ubuntu 12.04 LTS, ROS Fuerte and an intel graphics card.

gbd run output :

     (gdb) run
    Starting program: /opt/ros/fuerte/stacks/openni_tracker/bin/openni_tracker 
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
    [New Thread 0x7ffff1038700 (LWP 8120)]
    [New Thread 0x7ffff0837700 (LWP 8121)]
    [New Thread 0x7fffebfff700 (LWP 8122)]
    [New Thread 0x7fffeb7fe700 (LWP 8127)]
    [New Thread 0x7fffdf623700 (LWP 8133)]

    Program received signal SIGSEGV, Segmentation fault.
    0x00007fffe8a56e56 in Segmentation::detectionByPoint(bool, std::vector<Vector2D<int>, std::allocator<Vector2D<int> > > const*) ()
       from /usr/lib/libXnVFeatures_1_5_2.so


BT output :
#0  0x00007fffe8a56e56 in Segmentation::detectionByPoint(bool, std::vector<Vector2D<int>, std::allocator<Vector2D<int> > > const*) ()
   from /usr/lib/libXnVFeatures_1_5_2.so
#1  0x00007fffe8a61b61 in Segmentation::update(Array2D<unsigned short> const&, MotionDetectorByEdges const&, Floor const&, Farfield&, std::vector<Vector2D<int>, std::allocator<Vector2D<int> > > const*) ()
   from /usr/lib/libXnVFeatures_1_5_2.so
#2  0x00007fffe8a4769b in SceneAnalyzer::Update(std::vector<Vector2D<int>, std::allocator<Vector2D<int> > > const*, unsigned int) ()
   from /usr/lib/libXnVFeatures_1_5_2.so
#3  0x00007fffe8a0f95e in XnVSceneAnalyzer::InitFromSM() ()
   from /usr/lib/libXnVFeatures_1_5_2.so
#4  0x00007fffe8a107cb in XnVSceneAnalyzer::UpdateData() ()
   from /usr/lib/libXnVFeatures_1_5_2.so
#5  0x00007ffff6d315b7 in ?? () from /usr/lib/libOpenNI.so.0
#6  0x00007ffff6d3173e in ?? () from /usr/lib/libOpenNI.so.0
#7  0x00007ffff6d316b3 in ?? () from /usr/lib/libOpenNI.so.0
#8  0x00007ffff6d31965 in ?? () from /usr/lib/libOpenNI.so.0
#9  0x00007ffff6d31c0a in xnWaitAndUpdateAll () from /usr/lib/libOpenNI.so.0
#10 0x000000000040346b in WaitAndUpdateAll (this=<optimized out>)
    at /usr/include/ni/XnCppWrapper.h:9347
#11 main (argc=1, argv=<optimized out>)
    at /tmp/buildd/ros-fuerte-openni-tracker-0.1.3/debian/ros-fuerte-openni-tracker/opt/ros/fuerte/stacks/openni_tracker/src/openni_tracker.cpp:190

It also usually happens after I run it once succesfully. The first time it always runs OK, after that it may work once more, but the next will always segfault. After a reboot the same procedure occurs.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by AndreasLydakis
close date 2013-10-15 21:51:25

Comments

Can you post the backtrace?

mjcarroll gravatar imagemjcarroll ( 2013-06-12 10:54:38 -0500 )edit

Edited for BT and some details

AndreasLydakis gravatar imageAndreasLydakis ( 2013-06-12 22:53:58 -0500 )edit

I have the same problem than you, more details about when you get this error in my post : http://answers.ros.org/question/62873/openninite-segmentation-fault-with-openni_tracker/ but I didn't get any answer...

CarolineQ gravatar imageCarolineQ ( 2013-06-12 23:13:23 -0500 )edit
1

Since the first time it runs well, maybe the process XnSensorServer does not close properly. After closing the program, try to kill the XnSensorServer.

rastaxe gravatar imagerastaxe ( 2013-06-13 22:01:21 -0500 )edit

Thank you for your suggestion, I haven't been able to test it yet due to a power outage though. As soon as I can I will and post the results !

AndreasLydakis gravatar imageAndreasLydakis ( 2013-06-13 23:09:13 -0500 )edit

That actually seems to work ! I have been testing it for about an hour so far and it seems to do the job ! Thanks a bunch rastaxe ! BTW how do I mark this as solved and your answer as the solution ?

AndreasLydakis gravatar imageAndreasLydakis ( 2013-06-17 00:13:21 -0500 )edit

I am happy this works for you. I will put my comment directly in the answer section and you can set it as correct.

rastaxe gravatar imagerastaxe ( 2013-06-17 21:40:14 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
2

answered 2013-06-17 21:41:57 -0500

rastaxe gravatar image

Since the first time it runs well, maybe the process XnSensorServer does not close properly. After closing the program, try to kill the XnSensorServer.

edit flag offensive delete link more

Comments

This doesn't solve the problem for me... The problem is solved only if I re-plug the Kinect, which is not a good solution...

CarolineQ gravatar imageCarolineQ ( 2013-06-18 23:59:59 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2013-06-12 03:32:22 -0500

Seen: 837 times

Last updated: Jun 17 '13