Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regularly sync symbols to Ghidra #112

Open
robojumper opened this issue Nov 28, 2024 · 0 comments
Open

Regularly sync symbols to Ghidra #112

robojumper opened this issue Nov 28, 2024 · 0 comments

Comments

@robojumper
Copy link
Collaborator

robojumper commented Nov 28, 2024

With https://github.com/zeldaret/ss/blob/main/tools/ghidra_scripts/DecompMapToGhidra.py, we have a script that can take the map files produced by the decomp toolchain and apply them to a Ghidra project, correctly handling the relevant text and data sections in the main DOL and RELs. We should regularly do that, and this issue tracks the process.

The following steps should be followed:

  1. Check out the latest main commit
  2. Figure out the commit hash, e.g. git rev-parse HEAD
  3. Run ninja -t clean, python configure.py --map, ninja
  4. Make sure you have a matching, OK build for the main DOL and all RELs
  5. Check out the latest version of the Ghidra file
  6. Run the script, choosing build/SOUE01 for the build directory and entering the commit hash in the second popup
  7. Some symbols will fail to demangle. These should be limited to fake symbols that were originally ported from the Ghidra repo to the decomp
  8. Spot check the result: Symbols that haven't been changed since the last sync should not have their history modified, and new symbols should be present
  9. Check in the result

History of syncs

Date Ghidra file + version Commit hash
2024-11-28 NTSC-1.0 (15) 5dd7182
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant