Update Debugging with Ghidra on Linux

Lucas Schwiderski 2025-05-07 23:27:54 +02:00
parent 201f615720
commit 16611934d6
Signed by: Forgejo (git.sclu1034.dev)
GPG key ID: B1C9C29730D3D366

@ -1,5 +1,7 @@
> To be fleshed out, for now this is just me dumping steps as I do them > To be fleshed out, for now this is just me dumping steps as I do them
## Basic setup
1. Open the `darktide_launcher.log` and find the arguments to run the executable with. 1. Open the `darktide_launcher.log` and find the arguments to run the executable with.
At the time of writing: `-eac-untrusted --bundle-dir ../bundle --ini settings --backend-auth-service-url https://bsp-auth-prod.atoma.cloud --backend-title-service-url https://bsp-td-prod.atoma.cloud -game -launcher_verification_passed_crashify_property false` At the time of writing: `-eac-untrusted --bundle-dir ../bundle --ini settings --backend-auth-service-url https://bsp-auth-prod.atoma.cloud --backend-title-service-url https://bsp-td-prod.atoma.cloud -game -launcher_verification_passed_crashify_property false`
@ -25,3 +27,7 @@ STEAM_COMPAT_DATA_PATH=/path/to/SteamLibrary/steamapps/compatdata/1361210
5. Run the script in a terminal, it will echo `target remote <host>:<port>` 5. Run the script in a terminal, it will echo `target remote <host>:<port>`
6. In Ghidra, for the debugger configuration, choose "remote gdb", enter the port and run. Breakpoints should become available 6. In Ghidra, for the debugger configuration, choose "remote gdb", enter the port and run. Breakpoints should become available
7. Run `continue` (or just `c`) in the gdb terminal to start the game, or any other gdb command. 7. Run `continue` (or just `c`) in the gdb terminal to start the game, or any other gdb command.
## Observations
- Ghidra doesn't seem to set breakpoints automatically. Instead, the "Debug Console" window will talk about "there are breakpoints to place" and a button to do that