maddo/Crusader_Decomp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Pseudocode decompialtion improvements and docs

Browse source
This commit is contained in:
MaddoScientisto 2026-03-26 22:10:48 +01:00
commit 589bfc31ef
1898 changed files with 60634 additions and 6597 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.github/instructions/ghidra-mcp-server-updates.instructions.md vendored
View file

@ -22,6 +22,8 @@ Use these instructions when making changes in the local Ghidra MCP source at K:/
- Keep backward compatibility for endpoint naming when practical by adding aliases instead of removing old routes.
- Keep xref and analysis outputs machine-friendly and evidence-rich (addresses, ref type, classification, function context).
- **Terminal execution rule:** When running multi-line Python for testing or server-side scripts, do not paste multi-line code into interactive terminals. Always write the code to a temporary `.py` file and execute it with the Python interpreter. This prevents paste-related failures and preserves the intended execution environment.
## Verification Rules
- After server edits, run a Maven validation from K:/mcp/GhidraMCP.

3
.github/instructions/ghidra.instructions.md vendored
View file

@ -37,7 +37,8 @@ applyTo: "**"
- **Always use `rename_function_by_address`** — `rename_function` (by name) fails with "must have required property 'old_name'" and is broken. Use `"function_address": "000c:XXXX"` format.
- For substantive RE batches, end with at least 6 concrete future steps unless the task is fully closed and there are genuinely fewer defensible next actions.
- When a batch analyzes currently unnamed Ghidra functions and the behavior is clear enough, rename them in Ghidra instead of leaving them as positional `FUN_xxxx_xxxx` placeholders.
-
- **Terminal execution rule:** Always write multi-line Python scripts to a temporary `.py` file and execute that file with the Python interpreter instead of pasting multi-line Python directly into an interactive terminal. This avoids paste/encoding/line-ending issues and ensures the script runs in the expected environment.
# Executable Write Safety
- Normal Ghidra database work on `CRUSADER.EXE` remains in scope: renames, comments, prototypes, local-variable/type cleanup, function creation/deletion, and boundary repair are allowed unless the user says otherwise.