New jemalloc causes crashes - looking for ideas

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

Hey folks,

the switch to newer jemalloc in libc recently makes evbarm (v5) userland
fail with core dumps everywhere.

The minimum alignment (LG_QUANTUM 3, so 2^3 minimal alignement) did not
change.

Can someone educate me how to use the external symbols from in a cross-gdb?
I didn't get that part working, and it also seems to be unhappy with the
core file...

[..]
This GDB was configured as "--host=x86_64-unknown-netbsd10.99 --target=arm--netbsdelf-eabi".
[..]
(gdb) set sysroot /branches/hosts-current/evbearmv5/
(gdb) file /branches/hosts-current/evbearmv5/bin/sh
Reading symbols from /branches/hosts-current/evbearmv5/bin/sh...
(No debugging symbols found in /branches/hosts-current/evbearmv5/bin/sh)
(gdb) target core sh.core
warning: BFD: warning: /tmp/sh.core has a segment extending past end of file
[New process 11128]
Core was generated by `sh'.
Program terminated with signal SIGBUS, Bus error.
#0  0xbbef4f64 in ?? ()
(gdb) bt
#0  0xbbef4f64 in ?? ()
#1  0xbbef5434 in ?? ()
(gdb) x/i 0xbbef4f64
=> 0xbbef4f64:  Cannot access memory at address 0xbbef4f64
(gdb) info reg
r0             0xbbcb557c          3150665084
r1             0xbfffe384          3221218180
r2             0xbbefe548          3153061192
r3             0xbfffe338          3221218104
r4             0xbbee5140          3152957760
r5             0xbfffe33c          3221218108
r6             0x1                 1
r7             0xbfffe384          3221218180
r8             0x0                 0
r9             0x1                 1
r10            0xbfffe338          3221218104
r11            0xbfffe370          3221218160
r12            0x60                96
sp             0xbfffe2c4          0xbfffe2c4
lr             0xbbef5434          3153024052
pc             0xbbef4f64          0xbbef4f64
cpsr           0xa0000010          2684354576

Martin