After not building Ghidra locally for a while I've synced the source but can no longer step through it in the debugger

[hippietrail]

As in a previous question from some weeks back, I had to delete half a dozen sub-projects to get it to build, including some related to debugging.

But unlike that time I now can't step through code in the debugger. When it gets to where my breakpoint is it shows an error "Source not found." and an "Edit the source lookup path..." which has several options.

I chose "File System Directory" and selected the root directory of my clone of the Ghidra repo. But running it again I end up in the same place:

I don't know if this is related to:

• Having to delete some debugging projects from Ghidra to get it to build.
• Just happens sometimes when syncing?
• Choosing the wrong option when editing the source lookup path.
• Choosing the right option but wrong directory.
• Something else.

I'm not from the Java/Eclipse world and don't know how to proceed.

[d-millar]

@hippietrail I'm not sure if this was clear from @ryanmkurtz's post but deleting the various debugger directories should have been a one-off event. That is, we deprecated the GADP / IN-VM interfaces and removed them in advance of the latest release, so, if you upgraded from the code before they were deprecated to the code after, you would need to delete those.

Once things have gotten to be a bit of a mess, it's probably easiest to re-clone the repo and re-build. The instructions on github should suffice.

If this doesn't work for you, i.e. you still have errors, send us an errors you see in the Terminal, the Debug Console, or the console you launch Ghidra from (if you use "support/ghidraDebug" vs. "ghidraRun).

[hippietrail]

Ah OK well I'll reclone but I'm really worried about stuff that's committed but not pushed because of being in unfinished/broken/experimental state. Thanks.

[hippietrail]

After struggling a bit not knowing if I should/can have two clones of the repo in the same workspace I made a new workspace and did these steps in the terminal:

 3919  mkdir ghidra-repo-jan-2025
 3920  cd ghidra-repo-jan-2025
 3921  git clone https://github.com/hippietrail/ghidra.git
 3923  cd ghidra
 3928  gradle -I gradle/support/fetchDependencies.gradle
 3929  gradle buildGhidra 
 3930  gradle prepdev eclipse buildNatives

And in Eclipse: File/Import/Existing Projects into Workspace/

Once it was finished I have a number of entries that look like they're to do with dependencies but as you can see, I did the fetchDependencies step so I'm confused:

Note that I cloned my fork of Ghidra which I regularly sync with the original Ghidra. It just has a few of my own customizations but it's mostly to learn how to maintain a forked project on Github.

I'm bad at Git and GitHub as well as Eclipse though so I'm probably missing something obvious. Does my fork still include the deprecated debugger stuff somehow despite being synced? Some of the errors mention debugging but not of them mention GADP / IN-VM

---

Update I cloned the original Ghidra project as well and it builds just fine. I have no idea how my fork of the repo is broken when I always sync'ed it. I don't know where to start looking.

[Wall-AF]

You need to prepare for eclipse too. My command is:
gradle --init-script gradle/support/fetchDependencies.gradle cleanEclipse prepDev eclipse -PeclipsePDE buildNatives

[hippietrail]

Well I don't understand why I didn't have to do something like that before, but it certainly worked, so thank you!