Repository navigation
Debugging Tool PowerShell
← Debugging Tools and Commands
PowerShell coordinates Windows test launches, GUI-session helpers, hashing, process identity, WPR/WPA tools, bounded input, manifests, and cleanup.
| Property | Details |
|---|---|
| Supported OS | Windows, Linux, macOS; Windows is required for Windows-specific ETW and GUI orchestration. |
| Install | Install PowerShell or use Windows PowerShell where appropriate. |
| Verify | $PSVersionTable |
| Primary output | See the workflow below. |
PowerShell is used heavily to launch bounded workloads, invoke WPR/WPAExporter, capture process identity, hash files, and clean up owned helper processes.
Useful primitives:
Get-FileHash .\xemu.exe -Algorithm SHA256
Get-Process xemu -ErrorAction SilentlyContinue
Get-CimInstance Win32_Process | Where-Object Name -eq 'xemu.exe'
wpr -status collectors -detailsFor automation, record at least:
- PID;
- creation time;
- parent PID when available;
- originating command/run identity.
A remote command timing out does not prove the server-side process stopped. Always perform bounded cleanup checks.
Do not recursively kill generic python, powershell, wpa, or xperf processes unless ownership has been established; unrelated host tools may be active.
Automation output is not proof that the intended GUI action or guest state occurred. Verify window/session identity, guest progress, capture markers, and resulting artifacts.
A remote timeout does not stop the remote process. Clean up only processes owned by the run, using PID, creation time, parent PID, and command identity. Do not kill generic PowerShell, Python, WPA, or xemu processes without proving ownership.
- Tool name and exact version.
- Source commit/tree and executable SHA-256.
- The complete command or saved profile used.
- Input artifact hashes and the explicitly selected time or address range.
- Raw output plus any derived report; do not retain only a screenshot or conclusion.
- Admission failures, warnings, dropped events, incomplete rows, or unsupported operations.
DSP tooling guide and navigation updated November 2, 2026 for experimental PR #384, source 8f51d237. Capture/replay usage and limits.
The earlier wiki-wide review was published November 1, 2026. Emulator source: b7140848. Reviewed wiki content: 1d2b671. Current status · Release availability · Publication process.
- Home
- Current status
- Stable versus main
- Implemented mechanisms
- Controls and defaults
- Measured results and limits
- Complete change register
- System
- CPU and vCPU
- Memory and DMA
- Graphics / NV2A
- APU and audio
- Timing and timers
- Platform and I/O
- Hardware observations
- Fidelity boundaries
- Methodology
- PGR2 routes
- Debugging lag / hot paths
- Tools and commands
- DSP capture, replay and fuzzing
- HLE readiness and public XISO proof
- Concurrent DSP shadow and OpenAL proof
- DSP HLE operation inventory
- DSP HLE fix examples and testing
- Development
- Upstream shortlist
- Wiki maintenance
- Research / retired work
- Optimization catalog
- Hot-path shortcuts
- Researched experiments
- Unproven proposal directory
- PR lessons
- September26 snapshot
Repository · PRs · Issues