From a8b6ca1c379ce93b195bd336a74e3a5f4864ac35 Mon Sep 17 00:00:00 2001 From: Lucas Schwiderski Date: Thu, 8 May 2025 01:05:01 +0200 Subject: [PATCH] Update Debugging with Ghidra on Linux --- Debugging-with-Ghidra-on-Linux.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Debugging-with-Ghidra-on-Linux.md b/Debugging-with-Ghidra-on-Linux.md index f4cea60..afd37f2 100644 --- a/Debugging-with-Ghidra-on-Linux.md +++ b/Debugging-with-Ghidra-on-Linux.md @@ -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. @@ -30,4 +32,5 @@ 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 \ No newline at end of file +- 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 \ No newline at end of file