don't understand tip in section semihosting

Open
#149 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust

Research direction

Start with the semihosting page at rust-embedded.github.io/book/start/semihosting.html and investigate the quoted panicking behavior, no_std run-pass tests, and QEMU workflow. Clarify what setting panicking to exit(EXIT_FAILURE) means and how a reader would use it; the documentation is done when the tip is understandable and its expected result is reproducible.

Written by the indexing model from the issue text.

Description

https://rust-embedded.github.io/book/start/semihosting.html

One last tip: you can set the panicking behavior to exit(EXIT_FAILURE). This will let you write no_std run-pass tests that you can run on QEMU.

no idea what this is about or how it would work

Dominant language
No language data
Stars
1.3k
Forks
223
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from rust-embedded/book

All issues in rust-embedded/book

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.