Disconnect3d

Done in #2208

Fwiw bata24/GEF has sth implemented for this and I used it in the past, but I believe it can be improved. This may also be helpful: https://gist.github.com/disconnect3d/4fa1972f5b3148bf17995406490c0e70, at least to...

> I get an uneasy feeling this will only work for 64 bit architecture because of that hardcoded +16 +1. Also: don't we somehow support/know what's the metadata/allocated buffer offset...

@CptGibbon What should we do here? Can we just merge it and fix it in the future if it ever breaks? Shall we maybe do `+2*ptrsize` instead of `+16`?

I spoke with @dmur1 and let's just drop this for now. I don't think this feature is super needed, unless more people ask for that.

Fwiw there is some discussion around that on GEF Discord. GEF does not support this use case currently as well.

I bet we don't know the memory mappings and we either try to explore them, or, we try to dereference registers and that's what is happening.

A best practice which does not hurt the user and may as well educate them that it is important ;). Feel free to either accept or reject this PR. If...

Generally, this is a nice feature but it would add some complexity. The registers are (iirc) displayed via some telescope/dereference function (`pwndbg.chain`? `pwndbg.chain.format`?) and this also uses some kind of...

Does this setup provide vmmap information in pure GDB that u can fetch via `info proc mappings`? If so, it should probably just work 🤔