baidu / baidu/boteye_driver

关于读取yaml文件时出错的问题

Open
#5 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
3
Forks
6
PR merge metrics
No merged PRs in 30d

Description

您好,我在运行depth_demo时,会出现段错误,用gdb定位在yaml文件读取:

```
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe363b700 (LWP 19352)]
YAML::detail::node::get (this=0x7fffd41c71d0, key="DeviceId", pMemory=
std::shared_ptr (use count 7, weak count 0) = {...})
at /usr/local/include/yaml-cpp/node/detail/node_ref.h:25
25 NodeType::value type() const { return m_pData->type(); }
```

我的yaml文件如下:
```
DeviceId: ""
SensorType: UNKNOWN
Imu:
accel_TK:
- [1, 0, 0]
- [0, 1, 0]
- [0, 0, 1]
accel_bias: [0, 0, 0]
gyro_TK:
- [1, 0, 0]
- [0, 1, 0]
- [0, 0, 1]
gyro_bias: [0, 0, 0]
accel_noise_var: [0.0016, 0.0016, 0.0016]
angv_noise_var: [0.0001, 0.0001, 0.0001]
D_T_I:
- [1, 0, 0, 0]
- [0, 1, 0, 0]
- [0, 0, 1, 0]
- [0, 0, 0, 1]
```
 请问一下这个是yaml文件的问题,还是别的问题?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the crash in depth_demo under gdb and inspect the YAML read path leading to yaml-cpp's node_ref.h:25, using the reported DeviceId lookup as the entry point. Compare the supplied YAML with the fields depth_demo expects; done means identifying whether the configuration or another read-path issue causes the segmentation fault and recording a reproducible resolution.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.