Dan

A good bit of framework for this is already in place, specifically our trace database, but we have not yet gotten to automating this sort of analysis ourselves. To my...

Yeah, that solution makes sense, and it's what I'm considering. The idea of putting 'nosections' in there was to avoid having to pipe the section names at all, but that...

Because your local system is Windows and the remote Linux, I suspect it's a matter of the executable path not lining up when you use the Quick Launch button. You'll...

Yes, I did, but I'll try again. The only way I was able to reproduce the message you got was for the "file" command to fail. Can I get a...

A couple more bits of info that might help diagnose the issue: 1. Can you paste the contents of the "Interpreter" window after attempting to launch? 2. The example error...

Another shot in the dark: When prompted for the target executable path, there should also be a checkbox to "use starti." Enable it. It still doesn't explain the error message...

I like this suggestion, @cyrozap. My approach was more heuristic to begin with, I just hadn't considered extremely small memory spaces. I neglected to check the size at all :/...

The fact that anything other than Objects/Targets is populated means you're already recording, which is good news. (BTW, you can see you're recording in the Threads window. You'll see the...

Interesting that GDB names `tdata3` in particular.... A couple experiments to try: 1. In the Interpreter (or in vanilla gdb-multiarch) just try `print/x $tdata3` 2. In Ghidra's "Registers" window, there...

I just looked back at the original screenshot and noticed pc and sp are in the "Watches" window. I'm curious if you can cherry-pick other registers.... Try a third, say...