micro-ROS / micro-ROS/micro-ROS-Agent

run micro-ROS-Agent to connecct a client ,the terminal will report "terminate called after throwing an instance of 'std::bad_array_new_length' what(): std::bad_array_new_length"

Open
#205 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
201
Forks
111
Avg merge
1d 6h
Merged PRs (30d)
10

Description

## issue : std::bad_array_new_length

- Hardware description: longxin 2k with using longxin2k1000 CPU made in China.
- RTOS: ruihua RTOS made in China
- Installation type: micro_ros_setup
- Version or commit hash: humble

#### Steps to reproduce the issue
run MicroRos client to create a connection with micro-ROS-Agent, my terminal will report this problem.
but ,i can create a connection by using the humble micro-ROS-Agent in docker.
i just build micro-ROS-Agent by micro_ros_setup tool and run it

#### Expected behavior
like i use it in docker,work well
#### Actual behavior
![image](https://github.com/micro-ROS/micro-ROS-Agent/assets/42798006/3757ff71-20ef-4593-8bba-1e1a1070c2ec)
#### Additional information

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the micro-ROS client connection using the micro_ros_setup-built Agent on the Longxin 2K with Ruihua RTOS, then compare it with the working Humble Agent in Docker. No source files or tests are named; trace the Agent startup and connection path to identify where std::bad_array_new_length is raised. Done means the locally built Agent connects successfully without the exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
embedded-iot, robotics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.