Update Debugging with Ghidra on Linux
parent
16611934d6
commit
a8b6ca1c37
1 changed files with 4 additions and 1 deletions
|
@ -1,5 +1,7 @@
|
|||
> To be fleshed out, for now this is just me dumping steps as I do them
|
||||
|
||||
> Currently stuck at the fact that breakpoints don't seem to work
|
||||
|
||||
## Basic setup
|
||||
|
||||
1. Open the `darktide_launcher.log` and find the arguments to run the executable with.
|
||||
|
@ -31,3 +33,4 @@ STEAM_COMPAT_DATA_PATH=/path/to/SteamLibrary/steamapps/compatdata/1361210
|
|||
## 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
|
||||
- multi-process mode, e.g. when Ghidra attaches as `extended-remote`, or the gdbserver is started with `--multi`, should allow restarting the
|
Loading…
Add table
Add a link
Reference in a new issue