ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

Setting eveything to debug does not solve this... and changing optimization level also does not change anything correctly. It seems that it's only "luck" if changing build type solves the problem. i think its more a problem of armhf compiler alignment and ros cpp serialization. On armel everything worked fine for me, so i would guess it's the hard-float support.

Setting eveything to debug does not solve this... and changing optimization level also does not change anything correctly. It seems that it's only "luck" if changing build type solves the problem. i think its more a problem of armhf compiler alignment and ros cpp serialization. On armel everything worked fine for me, so i would guess it's the hard-float support.


Problem seems to be in de-/serialization! try to use NODELETS instead of NODES. intra-process-communictaion, makes no use of it and should work, hopefully... ;-) tried it, and it seemed to "fix" the alignment error problem.

Setting eveything to debug does not solve this... and changing optimization level also does not change anything correctly. It seems that it's only "luck" if changing build type solves the problem. i think its more a problem of armhf compiler alignment and ros cpp serialization. On armel everything worked fine for me, so i would guess it's the hard-float support.


Problem seems to be in de-/serialization! try to use NODELETS instead of NODES. intra-process-communictaion, makes no use of it and should work, hopefully... ;-) tried it, and it seemed to "fix" the alignment error problem.


nodelets doesn't work, too... try to use CodeSourcery Compiler with "-mno-unaligned-access"... doesn't tried it yet, but at end of the week i can tell more...