Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed a typo: replaced the version of cargo-size from 0.3.3 to 0.3.6 #13

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

wubin28
Copy link

@wubin28 wubin28 commented Nov 11, 2024

No description provided.

@wubin28 wubin28 requested a review from a team as a code owner November 11, 2024 11:39
Copy link
Member

@BartMassey BartMassey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks much! Better is probably

cargo install cargo-binutils --vers '^0.3'

to keep it current as things change.

@wubin28
Copy link
Author

wubin28 commented Nov 12, 2024

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!

@wubin28
Copy link
Author

wubin28 commented Nov 13, 2024

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.

@wubin28
Copy link
Author

wubin28 commented Nov 15, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants