Open wubin28 opened 2 weeks ago
The current documentation's ambiguity regarding the GDB command has caused significant confusion, particularly for newcomers to embedded Rust development. The text shows gdb in the command example, which can be misleading as this basic command often doesn't work for embedded development. In my own experience as a beginner, this led to a frustrating day-long debugging session, including reinstalling Ubuntu from 24.04 to 22.04, only to eventually discover that I needed to use gdb-multiarch instead of gdb on Ubuntu. A more helpful approach would be to provide explicit, OS-specific GDB commands in the note section, making it clear that Linux users need gdb-multiarch, while macOS and Windows users should use arm-none-eabi-gdb. This clarification would save other developers from similar time-consuming troubleshooting experiences.
The current documentation's ambiguity regarding the GDB command has caused significant confusion, particularly for newcomers to embedded Rust development. The text shows gdb in the command example, which can be misleading as this basic command often doesn't work for embedded development. In my own experience as a beginner, this led to a frustrating day-long debugging session, including reinstalling Ubuntu from 24.04 to 22.04, only to eventually discover that I needed to use gdb-multiarch instead of gdb on Ubuntu. A more helpful approach would be to provide explicit, OS-specific GDB commands in the note section, making it clear that Linux users need gdb-multiarch, while macOS and Windows users should use arm-none-eabi-gdb. This clarification would save other developers from similar time-consuming troubleshooting experiences.
I have removed commit 2393e6d
from this pull request as it was unrelated to the purpose of this PR. I may submit a separate PR for the changes introduced in 2393e6d
at a later time.
Hi @BartMassey, I’ve updated the cargo-size version specification as suggested. Let me know if there’s anything else needed. Thanks for the feedback!