On Thu, 13 Sep 2018, Richard Biener wrote: > On Thu, 13 Sep 2018, Gerald Pfeifer wrote: > > > On Mon, 10 Sep 2018, Martin Liška wrote: > > > Works for me! One needed to add --wrapper gdb81,--args. So now > > > I see a nice back-trace. > > > > Great! This appears to be a tough one, though breaking FreeBSD/i386 > > with clang, GCC 6 and GCC 9 (two weeks old), Solaris, HP/UX, so looks > > like something around glibc vs other libcs? > > > > > > On FreeBSD 10.4 I tried malloc debugging setting MALLOC_CONF=zero:true > > in the environment, to zero initialize all allocations, alas that also > > did not change anything. > > > > Nor did MALLOC_CONF=tcache:false,junk:true. > > > > So my guess is it's a memory allocation issue, but perhaps one level > > higher than the system functions? > > > > > > Not sure how I can help; clearly not my area of expertise. :-( > > If it reproduces with clang as a host compiler maybe you can > use ASAN with it? I'm not sure if GCCs ASAN support is up to speed. > IIRC the issues all show up with the stage1 compiler... > > Martin's now gone and I have to try set up a VM with FreeBSD to > debug this myself.
So I can reproduce with a different backtrace using gcc 6.4.0 as host compiler (and FreeBSD 10.4). I can't seem to bootstrap using clang (3.4.1) though. IIRC Martin claimed newer FreeBSD are OK for non-obvious reasons (I see the jemalloc versions are different between FreeBSD releases). It probably makes sense to build a libc with debuginfo and configure jemalloc with debugging, I will try that now... Richard.
