FIESTA icon indicating copy to clipboard operation
FIESTA copied to clipboard

Crashed on ubuntu 18

Open JINXER000 opened this issue 3 years ago • 0 comments

I am testing this program on ubuntu 18, Xavier NX. Any launch will crash with an segment fault and I cannot find why.

I used valgrind to test it, which outputs the log as follows:

==23003== Memcheck, a memory error detector
==23003== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==23003== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==23003== Command: /home/microhiggs/yzchen_ws/yzchen_ws_tx2/fiesta/devel/lib/fiesta/test_fiesta ~depth:=/camera/depth_registered/points ~transform:=/kinect/vrpn_client/estimated_transform __name:=fiesta __log:=/home/microhiggs/.ros/log/7710de6a-cb76-11eb-b46e-70665563cf6d/fiesta-1.log
==23003== Parent PID: 22987
==23003== 
==23003== Invalid read of size 8
==23003==    at 0x49AFF98: ros::CallbackQueue::callAvailable(ros::WallDuration) (in /opt/ros/melodic/lib/libroscpp.so)
==23003==    by 0x4A03DEB: ros::SingleThreadedSpinner::spin(ros::CallbackQueue*) (in /opt/ros/melodic/lib/libroscpp.so)
==23003==    by 0x49EDA47: ros::spin() (in /opt/ros/melodic/lib/libroscpp.so)
==23003==    by 0x12705F: main (in /home/microhiggs/yzchen_ws/yzchen_ws_tx2/fiesta/devel/lib/fiesta/test_fiesta)
==23003==  Address 0x18 is not stack'd, malloc'd or (recently) free'd
==23003== 
==23003== 
==23003== Process terminating with default action of signal 11 (SIGSEGV)
==23003==  Access not within mapped region at address 0x18
==23003==    at 0x49AFF98: ros::CallbackQueue::callAvailable(ros::WallDuration) (in /opt/ros/melodic/lib/libroscpp.so)
==23003==    by 0x4A03DEB: ros::SingleThreadedSpinner::spin(ros::CallbackQueue*) (in /opt/ros/melodic/lib/libroscpp.so)
==23003==    by 0x49EDA47: ros::spin() (in /opt/ros/melodic/lib/libroscpp.so)
==23003==    by 0x12705F: main (in /home/microhiggs/yzchen_ws/yzchen_ws_tx2/fiesta/devel/lib/fiesta/test_fiesta)
==23003==  If you believe this happened as a result of a stack
==23003==  overflow in your program's main thread (unlikely but
==23003==  possible), you can try to increase the size of the
==23003==  main thread stack using the --main-stacksize= flag.
==23003==  The main thread stack size used in this run was 8388608.
==23003== 
==23003== HEAP SUMMARY:
==23003==     in use at exit: 60,222,044 bytes in 696 blocks
==23003==   total heap usage: 5,694 allocs, 4,998 frees, 60,656,379 bytes allocated
==23003== 
==23003== LEAK SUMMARY:
==23003==    definitely lost: 16 bytes in 1 blocks
==23003==    indirectly lost: 0 bytes in 0 blocks
==23003==      possibly lost: 101,407 bytes in 34 blocks
==23003==    still reachable: 60,120,621 bytes in 661 blocks
==23003==         suppressed: 0 bytes in 0 blocks
==23003== Rerun with --leak-check=full to see details of leaked memory
==23003== 
==23003== For counts of detected and suppressed errors, rerun with: -v
==23003== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

Could anyone help? Thanks.

JINXER000 avatar Jun 12 '21 13:06 JINXER000