[erlang-questions] Understanding etp-heapdump output in gdb

[Roger Lipscombe]

That fixed it. I also had to set $etp_max_depth to something ludicrous.

I'll look into doing a PR against master.

Thanks,
Roger.

On 19 December 2017 at 15:28, Lukas Larsson <lukas@REDACTED> wrote:
>
>
> On Tue, Dec 19, 2017 at 3:53 PM, Roger Lipscombe <roger@REDACTED>
> wrote:
>>
>> Thanks. Are those values relative to something? I'm seeing:
>>
>> [#RefcBinary<0x10,0x17079e08,0x39700560,0x39700578,0>,
>>  #RefcBinary<0x10,0x17079d68,0x39448c70,0x39448c88,0>,
>> ...etc.
>>
>> Those values look a little bit short for a 64-bit BEAM, or have I just
>> got holes in my core dump? Can you *have* holes in a core dump on
>> Linux?
>
>
> They seem to be truncated on 64-bit. Open etp-commands, look for function
> called etp-boxed-immediate-1, and change any "%#x" to "%p" and it should
> print the entire pointer.
>
> PR's to make etp work better in 32/64 bits are welcome :)
>
> Lukas
>