Re: jemalloc fallout for i386 on amd64?

[Martin Husemann <martin%duskware.de@localhost>]

On Sun, May 12, 2019 at 04:43:45AM +0300, Valery Ushakov wrote:
> I have an old i386 kmk binary built on 6.1

> Core was generated by `kmk'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0xf618abc9 in je_tcache_bin_flush_large () from /usr/lib/i386/libc.so.12
> (gdb) bt
> #0  0xf618abc9 in je_tcache_bin_flush_large () from /usr/lib/i386/libc.so.12
> #1  0xf618b6f0 in je_tcache_event_hard () from /usr/lib/i386/libc.so.12
> #2  0xf61f5712 in ?? () from /usr/lib/i386/libc.so.12
> #3  0xf61f72d7 in je_arena_ralloc () from /usr/lib/i386/libc.so.12
> #4  0xf6201f9f in realloc () from /usr/lib/i386/libc.so.12
> #5  0x08073908 in xrealloc (ptr=0xf5910e00, size=<optimized out>)
>     at kbuild/kbuild-trunk/src/kmk/misc.c:569

My bet would be: 0xf5910e00 is not a proper pointer returned from malloc
(or friends) before (that is: bug in kmk).

Martin