Open christian-rauch opened 3 years ago
I recommend you double-check that the RobotState isn't corrupted. I had a segfault with a nearly-identical stack trace and it was because there were NaN values in the collision body transforms.
Thanks for the hint. Back when this happened it was reproducible, but I actually cannot remember what I did back then, so it is technically not reproducible anymore :-)
Anyway, in such situations, it would be useful to check the input and print an error or throw an exception (that is caught by .g. RViz) instead of tearing down the process.
I am using fcl 0.5 through RViz and recently got a reproducible crash: