Disconnect3d

Hey, I finally got it launched. The thing is... it might require some work to make it work properly, but lets see what are the problems: 1) `ERROR: Could not...

Also, things described here might be helpful: https://github.com/pwndbg/pwndbg/issues/168

If you have the issue then I guess not. This seems to boil down as a "we cant get memory mappings properly" issue. There was an improvement in getting memory...

Also, this should be possible but probably not that easy to work around this issue by removing few things... mainly: - memory exploration - so, commenting out/removing this code: https://github.com/pwndbg/pwndbg/blob/dev/pwndbg/vmmap.py#L120-L124...

I would be happy to review and merge patches that make pwndbg more robust against debugging kernels with sources etc.

Hey, can you show the output of this command?: ``` monitor info mem ``` As a workaround, please comment out this line: ``` File "/home/user/projects/pwndbg/pwndbg/vmmap.py", line 51, in get pages.extend(monitor_info_mem())...

To elaborate a bit more - the issue with debugging linux kernel is that we don't have a proper place to fetch memory pages information from, so... we do it...

Btw the comments here might give some more context on the `monitor info mem` and its problems: https://github.com/pwndbg/pwndbg/pull/685

This is also broken in `add_main_exe_to_symbols` - its `gdb.execute` makes binaries with PIE (Position Independent Executable) segfaulting at some point. This stuff can be tested using such C code compiled...

Just to be sure, can you check if this happens on a previous commit, that doesn't include the `is_remote` change? :D