While not all exit codes provide enough information to troubleshoot from the codes directly, users encountering these issues should read the STACKDUMP traces as often there are keywords to help determine the cause of various issues.
When codes do not contain useful or enough information, investigate the task being performed right before the error occurred, and investigate relevant files to that section of processing.
Some examples:
"Polygon" and "Extent" listed, indicates issue with the processing extent.
ZN10OGRPolygon15getExteriorRingEv ZN5GRYFN6Extent4implC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
"VelodyneData...PositionPacket" listed, indicates an issue with Velodyne packet capture (GPS issues), or, if the system has an Ouster LiDAR, the configuration JSON file is either missing or empty.
ZN5GRYFN5LIDAR12VelodyneData14PositionPacketC1ERKS2_
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article