How to pass program parameters to Ghidra's debugger (WinDbg via GADP/TCP)

[oa2013]

Hi! I've built the debugger branch and I can't figure out how to pass program parameters to the debugger.

Is that done through the interpreter window or before the debugger (WinDbg via GADP/TCP option) is connected? Below are my two screenshots:

[d-millar]

@oa2013 Hi, and there are probably a couple of answers to your question - hopefully one is the one you're looking for....

If you want to pass parameters to the program you're debugging, the easiest way is:
(1) connect to the agent you prefer
(2) in the Objects view, choose the "Launch (X)" button from the menu bar
(3) enter the executable name with full path and the parameters you wish to pass

If you want to pass parameters specific to a particular kind of launch:
(1) connect to the agent
(2) open up "Connections"
(3) select the connector you want
(4) hit the "Launch (X)" button and provide the parameters specific to that connector

If you want to pass parameters to the agent itself, e.g. you're connecting to a remote server
(1) open one of the GADP agents
(2) in the "DebugConnect options (.server)" entry, add the parameters, e.g. tcp:port=54321

Let us know if none of these do the trick and/or if you ideas about a better way to do what you want. We're still experimenting a bit with this!

D

[ryanmkurtz]

and I hope it gets integrated into the main branch soon.

I just wanted to add the the debugger is currently in the master branch

[oa2013]

Regarding the syncing, here is what I mean - and I don't know if this is possible, of course - but if I have both the CodeBrowser and the Debugger windows open, I want to see the breakpoint from the debugger in the decompiled view:

If this is a possibility in the future, I would be happy to put in a feature request. Thanks so much again, guys and girls!

[d-millar]

Ah, got it! Yeah, I don't think breakpoints show up in the decompiler no matter what you do. Will add that to the ticket I just put in re Dynamic view not tracking in the Decompiler.

You may have already figured this out, but you can get the CodeBrowser to track progress in the Debugger. I mention it as it's not terribly obvious. In the FrontEnd->Tools->Connect Tools..., you can pick any tool combination and connect events between them.

[oa2013]

Awesome! I've now connected the two tools and can see the decompiled code within the debugger. To add to that ticket, in addition to seeing the breakpoint, I'd also like to the decompile view to highlight the appropriate line of code as I use the step-through the code buttons on the left (like Visual Studio or Eclipse).

But even without that, being able to see both the decompiled code and the debugger in one integrated window is huge - thanks for making that happen!

[d-millar]

Cool - will add. When it does track, I think the little yellow blip in the decompiler is actually trying to follow the assembly. It's not the entire line, I believe, because it's trying to suggest where in the instruction you are. Nevertheless, an option here might be nice!