RT-Thread / RT-Thread/rt-thread
windows vscode qemu-dbg.bat: unable to start debugging unexepected GDB output from command ... connection time out
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 12.2k
- Forks
- 5.4k
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 40
Description
rt-thread-lts-v4.1.x\bsp\qemu-vexpress-a9
按照官网步骤一步步来，windows 下 vscode qemu-dbg.bat 无法进行调试。大家有没有遇到啊。网上尝试搜索，试了好几天。没有解决。这是什么问题。盼遇到过这个问题的专家帮助解决一下。
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 with rt-thread-lts-v4.1.x\bsp\qemu-vexpress-a9 and the Windows qemu-dbg.bat script, then compare its VS Code debugging command with the unexpected GDB output shown in the screenshots. Reproduce the connection timeout on Windows and trace the command invocation. Done means qemu-dbg.bat starts the debugger successfully for this BSP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, vscode
- Domain
- devtools, embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100