Failed status on line 81: 1. Aborting.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- embedded-iot
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.
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
- Dominant language
- C
- Stars
- 419
- Forks
- 123
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from micro-ROS/micro_ros_espidf_component
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
micro-ROS/micro_ros_espidf_component#336 · 3 comments ·
-
The issue of porting esp32p4Possibly taken @Narukara claimed this 131 days ago. Open
micro-ROS/micro_ros_espidf_component#314 · 3 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
micro-ROS/micro_ros_espidf_component#310 · 2 comments ·
All issues in micro-ROS/micro_ros_espidf_component
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
EchoTools/nevr-runtime#117 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
DarkFlippers/qUnleashed#240 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
AFLplusplus/AFLplusplus#2899 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
HarbourMasters/Shipwright#7320 ·
Maintainers usually reply within 1 day