Closed johannes-fischer closed 4 months ago
If allConflictingInMap is called twice on the same Route object, it produces a segmentation fault. The call to allConflictingInMap itself does not fail, but accessing the returned lanelet::ConstLaneletOrAreas object.
allConflictingInMap
Route
lanelet::ConstLaneletOrAreas
Code reproducing this behavior can be found here.
I can imagine this is caused by allConflictingInMap concatenating some iterators.
If
allConflictingInMap
is called twice on the sameRoute
object, it produces a segmentation fault. The call toallConflictingInMap
itself does not fail, but accessing the returnedlanelet::ConstLaneletOrAreas
object.Code reproducing this behavior can be found here.
I can imagine this is caused by
allConflictingInMap
concatenating some iterators.