Add `rust objdump` or `rust dis` for dissecting / disassembling generated libraries
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Monday Jun 03, 2013 at 17:02 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/6912
This issue was labelled with: A-an-interesting-project, A-tools in the Rust repository
We may or may not already have objdump like facilities available, but I do not see them in the help text for rust.
There is a small inspection facility in rustc: rustc --ls <library-crate>. This just scratches the surface of what I might want to see, though.
I also see rustc::metadata::creader::dump_crates, but I do not think that is a real disassembler either.
Contributor guide
No contributing guide indexed for this repository
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
Review the earlier discussion in issue #6912, then inspect the existing rustc --ls <library-crate> facility and rustc::metadata::creader::dump_crates. The issue names no files or tests and does not define the command's scope, so first establish the desired inspection and disassembly behavior before implementation; done requires an agreed command interface and verification against generated libraries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100