micro-ROS / micro-ROS/micro_ros_espidf_component
Failed status on line 81: 1. Aborting.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 419
- Forks
- 124
- Avg merge
- 21h 35m
- Merged PRs (30d)
- 3
Description
There are no issues with compilation and burning, and it can also connect to WiFi, but it starts up
RCCHECK(rclc_support_init_with_options(&support, 0, NULL, &init_options, &allocator));
Will report an error:
Failed status on line 81: 1. Aborting.
Strangely, the version I copied from Git yesterday can start normally, but rmw_microros/rmw_microros. h is not available.
After copying again today, this problem occurred
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the Git version that worked with the later copy, focusing on the rclc_support_init_with_options call and the reported rmw_microros/rmw_microros.h availability. Reproduce the startup failure and identify the version or file difference that causes status 1; done means the component starts normally with the expected header available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100