Configure debugging of the Rust wavec Whale and Vex binaries

Aperta
  • Qualcosa non va?
#87 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
50/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
developer-experience

Direzione di ricerca

Start with dependency issue #86 and related WfP issues #30, #32 and #33 to see what debug/launch and Cargo-execution infrastructure already exists in this repo, then find the code that assembles debug launch requests. Use the three linked Cargo.toml files (Wave, Whale, Vex) as reference fixtures for package/bin/test artifact selection and the fake Cargo/DAP outputs mentioned in the criteria. Done means executables are resolved from build results, stale/missing artifacts are reported instead of launched, and launch-request tests pass.

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

Descrizione

debugger enhancement help wanted priority high rust

Problem / current evidence

All three ecosystem tools are Rust/Cargo projects. Existing WfP #33 covers Cargo execution, but it does not select a compiler executable and reproduction arguments for a native debug launch.

Code and contract references

Scope / proposed contract

Add compiler-development debug configurations that select Cargo package/bin or test artifacts and connect them to the chosen debugger. Reuse Cargo workspace/artifact discovery instead of guessing target/debug paths.

Completion criteria

  • Resolve the actual selected executable/artifact from build results, including custom target directories and multiple packages.
  • Persist reproduction inputs, cwd, arguments and environment without shell interpolation.
  • Do not launch an old executable after a failed prerequisite build; show stale/missing artifact state.
  • Keep debugging wavec/whale/vex distinct from debugging the program they generate.
  • Document debug-info requirements for Rust builds and test launch requests with fake Cargo/DAP outputs.

Dependencies and boundaries

  • Depends on #86.
  • Reuse/coordinate with existing WfP work: #30, #32, #33.
  • Ecosystem index: #49; existing foundations: #8.

Difficulty

Medium — requires understanding the affected tool or platform integration.

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.