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

Lukas Larsson lukas@REDACTED
Tue Dec 19 16:28:07 CET 2017

On Tue, Dec 19, 2017 at 3:53 PM, Roger Lipscombe <roger@REDACTED>

> 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 :)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20171219/87cb10c1/attachment.htm>

More information about the erlang-questions mailing list