[GH-ISSUE #1992] Ghidra launch failures surface no actionable diagnostics (macOS) #663

New issue

Closed

opened 2026-10-15 18:27:04 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:27:04 +00:00

Owner

Originally created by @EDMND-SRC on GitHub (Oct 11, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/1992

Observed on REA 6.4.0, macOS 14.8.9 x64, Ghidra 12.1.4, Temurin JDK 21.0.11.

A failing Ghidra JVM launch returns failure_cause with only name GhidraLaunchError plus message Ghidra headless launch failed, with no exit code, launcher output, or JVM stderr retained. The same session manual run of support/analyzeHeadless started fine, so the real fault was in REA process spawning, but nothing in the result pointed there.

Contrast: provider selection failures in the same version return rich envelopes with per provider codes, reasons, and diagnostics.

Request: retain launcher command outcome detail (exit or signal plus bounded output) in launch failure diagnostics, the same way unexpected request failures already retain internal causes.

Originally created by @EDMND-SRC on GitHub (Oct 11, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/1992 Observed on REA 6.4.0, macOS 14.8.9 x64, Ghidra 12.1.4, Temurin JDK 21.0.11. A failing Ghidra JVM launch returns failure_cause with only name GhidraLaunchError plus message Ghidra headless launch failed, with no exit code, launcher output, or JVM stderr retained. The same session manual run of support/analyzeHeadless started fine, so the real fault was in REA process spawning, but nothing in the result pointed there. Contrast: provider selection failures in the same version return rich envelopes with per provider codes, reasons, and diagnostics. Request: retain launcher command outcome detail (exit or signal plus bounded output) in launch failure diagnostics, the same way unexpected request failures already retain internal causes.

bsakaguchi

2026-10-15 18:27:04 +00:00