Disconnect3d

This being said, debugging via qemu-user is kinda broken for now as we don't determine memory pages well.

Hey, I am not familiar with the Ghidra integration but I'd be happy to merge a fix for this issue. also cc: @anthraxx did u maybe work with this?

I think you would have to add this architecture to pwndbg and describe its register set etc similarly to https://github.com/pwndbg/pwndbg/blob/dev/pwndbg/regs.py#L136-L153

The bug occurs only if `silent` is present in the script. I am not sure yet what does it change.

A stupid stupid workaround, which is still not a great solution: modify the gdbscript breakpoint command to call the `continue` via python interpreter instead, like this: `pi gdb.execute("continue")`. With this,...

Another solution: implement the breakpoint via `gdb.Breakpoint` Python API. This way, we can say that the inferior **must not stop on the breakpoint but it will still execute our logic**....

``` pwndbg> help x Examine memory: x/FMT ADDRESS. ADDRESS is an expression for the memory address to examine. FMT is a repeat count followed by a format letter and a...

@RageYL Can you look if we can determine somehow whether we are debugging bare metal or not? Maybe there is some kind of `info ...` command that gives us such...

@RageYL Can you check `show osabi` after connecting to remote target? Someone mentioned this on #gdb IRC channel on freenode.

So maybe this is how we can determine debugging bare metal: ```python is_bare_metal = '(currently "none")' in gdb.execute('show osabi', to_string=True) ``` For me (without debugging bare metal) it is: ```...