Disconnect3d

Added in https://github.com/pwndbg/pwndbg/commit/d2b2523695a19b85487b91659668b7a94e84dc6c Shall we close this issue? WDYT about X29?

We could maybe add a TIP informing about it here: https://github.com/pwndbg/pwndbg/blob/dev/pwndbg/tips.py#L3-L9 :D

@junknet Fixed in #1054. Thanks for reporting this and looking into it!

I am not sure I get what it changes :D. Can you show a screen before/after or how can I reproduce the 'bad' behavior?

If you do: `gdb` and then `attach ` then it does not occur. It occurs in a `gdb -p ` case.

I still don't quite understand why this fixes the problem, but it fixes it, so thanks a lot for it! :)

@gsingh93 can you add the code related to it to our heap code? also, u should probably rely on the latest heap PR (we will merge it soon)

Ugh, sorry for not merging it earlier. Thanks a lot for this. I'm up for upgrading it to 8.x if that needs to be done as well.

``` ipdb> gdb.execute('show print elements', from_tty=True, to_string=True) '++show print elements\nLimit on string chars or array elements to print is 200.\n' ipdb> gdb.execute('show print elements', from_tty=False, to_string=True) '++show print elements\nLimit on...

It seems we should wrap gdb.execute into something that is able to recognize that trace-command was enabled