Dan

Ah! I know what's going on. There's logic in the launcher, if no mapping to the current program database appears after a timeout, it will attempt a Map by Module,...

Thanks for pointing it out. You were right about the hardcoding. I think I'll have the launchers all adhere to the Auto-Map setting.

Okay, so I've worked out the part to have the launchers adhere to the auto-map setting. However, I'm having trouble re-creating the second part about the problematic mapping not getting...

Unfortunately, I suspect that "Refresh" step will have to remain manual. We don't load section info in the gdb plugin by default, because it can be very costly, depending on...

FWIW, another alternative you might try, if you only need to refresh sections immediately after launch, it to copy and modify the gdb+qemu launcher script. The original is called `qemu-gdb.sh`....

That's a decent idea. Go ahead and put in the PR, and we'll consider it.

You'll need to define for the emulator what the `LOCK` pcode userop means. See https://github.com/NationalSecurityAgency/ghidra/blob/master/GhidraDocs/GhidraClass/Debugger/B4-Modeling.md. That tutorial goes into quite a bit more than you need, but essentialy, create a...

Essentially, the same solution as found here, but for a different processor: https://github.com/NationalSecurityAgency/ghidra/issues/6089. It's very possible your definition is effectively a NOP.

There's no longer a debugger-specific log file. (There used to be one that showed the GDB/MI conversation, but that was for gdb only.) Instead, the Terminal window may have important...

Oof. A lot can happen in two weeks! Okay, so if I understand things correctly up to this point, we've switched over to using the Python-based dbgeng, using a new/custom...