-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Closed
Labels
Description
Bug report
Required Info:
- Operating System:
- Ubuntu 20.04.2 LTS
- ROS2 Version:
- Foxy
- Version or commit hash:
- DDS implementation:
- default
Steps to reproduce issue
I had done some tests.These are mainly owing to malformed messages from laser sensor.
try {
// in fact, the function will throw std::rumtime_error in some situation,
// but the exception is not caught.
projector_.transformLaserScanToPointCloud(message->header.frame_id, *message, cloud, *tf_);
} catch (tf2::TransformException & ex) {
...
projector_.projectLaser(*message, cloud);
}
Expected behavior
Process should not crash.
Actual behavior
amcl:
amcl lifecycle node launched.
Waiting on external lifecycle transitions to activate
See https://design.ros2.org/articles/node_lifecycle.html for more information.
terminate called after throwing an instance of 'std::runtime_error'
what(): cannot store a negative time point in rclcpp::Time
controller_server:
controller_server lifecycle node launched.
Waiting on external lifecycle transitions to activate
See https://design.ros2.org/articles/node_lifecycle.html for more information.
local_costmap lifecycle node launched.
Waiting on external lifecycle transitions to activate
See https://design.ros2.org/articles/node_lifecycle.html for more information.
terminate called after throwing an instance of 'std::runtime_error'
what(): cannot store a negative time point in rclcpp::Time
planner_server:
planner_server lifecycle node launched.
Waiting on external lifecycle transitions to activate
See https://design.ros2.org/articles/node_lifecycle.html for more information.
global_costmap lifecycle node launched.
Waiting on external lifecycle transitions to activate
See https://design.ros2.org/articles/node_lifecycle.html for more information.
terminate called after throwing an instance of 'std::runtime_error'
what(): cannot store a negative time point in rclcpp::Time
Additional information
In fact, there are the same problems in ros1 navigation.
ros-planning/navigation#1151
Reactions are currently unavailable