Disconnect3d

And they are not? :P at least on dev branch

@k4lizen If symbols are there, we resolve the `tcache` symbol address as follows: https://github.com/pwndbg/pwndbg/blob/c72b0b6c3da479a999e395e3e432d33d037bbe84/pwndbg/gdblib/heap/ptmalloc.py#L1569-L1572 This resolves the symbol using GDB API: https://github.com/pwndbg/pwndbg/blob/c72b0b6c3da479a999e395e3e432d33d037bbe84/pwndbg/gdblib/symbol.py#L161-L171 Or in a more complex way: https://github.com/pwndbg/pwndbg/blob/c72b0b6c3da479a999e395e3e432d33d037bbe84/pwndbg/gdblib/symbol.py#L134-L158 Now,...

```c #include #include int tcache = 1; void foo(int tcache) { printf("Local tcache=%d\n", tcache); { int tcache = tcache + 1; printf("shadowed tcache = %d\n", tcache); asm("int $3\t\n"); } }...

hmm @k4lizen is this still broken? I can't reproduce this bug on: ``` Gdb: 13.1 Python: 3.11.4 (main, Dec 7 2023, 15:43:41) [GCC 12.3.0] Pwndbg: 2024.02.14 build: c72b0b6c Capstone: 5.0.1280...

Wdym that `nearpc` works? Does it work with source?

Hm... I guess we should then extend its description with another line describing the `[pc]` being `[lines]` if its small enough.

This is weird. Can this be because of using gdbserver? Maybe using gdbserver we can produce a minimal example?

@Aplet123 sounds good to me.

Some of this wa done in #2460. However, this is still really weird or maybe even wrong?: ``` pwndbg> search 0x0 Searching for byte: b'0x0' ld-linux-x86-64.so.2 0x7ffff7ff3417 0x3d732500307830 /* '0x0'...

Bump. We also got bitten by it in https://github.com/pwndbg/pwndbg/pull/3002#issuecomment-2902112623. > You might want to consider [using pytest-reportlog](https://github.com/pytest-dev/pytest-reportlog) or writing a custom plugin to get the output in whatever way you...