Dan

@clearbluejar I saw your blog post that led you to this bug: https://clearbluejar.github.io/posts/decompilation-debugging-pretending-all-binaries-come-with-source-code/ . Thanks for the thorough write-up! We haven't yet "ported" our tutorial to Windows, and it's also...

I can confirm that it's because the reported module size is too big. The TEB analyzer creates an artificial memory block, and the module mapper is mistaking it for an...

This was addressed in #5203, and I'd argue the double quotes thing is working as designed. I think the problem is that when we construct the command line for the...

The emulator has changed quite a bit from 10.2.3 to 10.3. Can you confirm this is still an issue in 10.3?

Interesting. Thanks for the full stack trace, as it explains why (perhaps) this error isn't caught in our unit tests. The error is actually produced by the "Stack" window. For...

OK. Nevermind my previous advice. It happens in a lot of UI components. I've started working on a patch.

Yeah, this gets a bit dicey, since in the end, the patcher is just modifying the bytes. Bytes can also be modified directly from the hex (bytes) viewer. As @ryanmkurtz...

This is neither optimized nor tested, but should provide the gist of how you might do it with a script: ```java public class ListPatchesScript extends GhidraScript { @Override protected void...

My recollection when we examined DAP is that it wasn't well suited for systems level debugging, which we're still aspiring for, eventually. I was familiar with it's support for GDB,...

That's a decent idea. FWIW, an alternative is to create an uninitialized block called "STACK" in the Memory Map. The SP should get initialized to the highest address (maybe +1)...