Add explicit object disassembly with address symbol and byte navigation

Aperta
#73 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
devtools

Direzione di ricerca

Start from the two linked references: Whale/src/commands/asm.rs (existing assembly inspection command) and the CLI wiring at Wave/src/cli.rs around line 1936, to see how commands are registered and how object files are passed in. Before any code, resolve or read the blocking dependencies (#69, #52, #50), since they define the contracts this work must honor. Done looks like a read-only disassembly path that validates backend and architecture first, renders address/instruction/bytes/symbols with explicit handling of data regions and undecodable bytes, and is covered by captured adapter-parsing fixtures with documented backend version compatibility.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

assembler debugger enhancement help wanted object priority medium

Problem / current evidence

Compiler contributors need to inspect emitted machine instructions, but WfP's assembly text highlighting is not a binary disassembler and Whale does not expose a disassembly CLI.

Code and contract references

Scope / proposed contract

Integrate an explicitly selected maintained disassembler backend for the initial supported object/ISA subset. Present address, instruction, bytes and symbols without claiming source mapping where none exists.

Completion criteria

  • Validate backend availability and object architecture before invoking it.
  • Keep disassembly read-only and never execute the inspected program.
  • Handle non-code/data regions and undecodable bytes explicitly.
  • Navigate between validated file/section ranges, symbols and instructions.
  • Keep output bounded/cancellable and test adapter parsing with captured fixtures; document backend/version compatibility.

Dependencies and boundaries

  • Depends on #69.
  • Depends on #52.
  • Depends on #50.
  • Ecosystem index: #49; existing foundations: #8.

Difficulty

High — spans compiler contracts, process/debugger lifecycle or structured inspection.

Audit baseline: Wave 509a1e46; Whale e3a12d08; Vex 71f29daa; WfP 2804fc02. This issue records source-audit findings and proposed work; no implementation or new execution is claimed. The checks above are future acceptance criteria. Prefer small fixtures and targeted validation; full builds or real debugger/IDE sessions should be explicit and necessary.

Lingua principale
Java
Stelle
0
Fork
3
Merge medio
8h 8m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di wavefnd/wave-for-platform

Tutte le issue di wavefnd/wave-for-platform

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.