On Sun, May 17, 2015 at 12:26:48PM +0100, Stuart Henderson wrote: > > (gdb) bt > #0 0x000017cf21e32181 in je_tsd_cleanup () from > /usr/obj/ports/rust-1.0.0/rust-stage0/bin/rustc > #1 0x000017d21b150056 in _rthread_tls_destructors (thread=0x17d17efaaa00) > at /usr/src/lib/librthread/rthread_tls.c:172 > #2 0x000017d21b14e872 in pthread_exit (retval=Variable "retval" is not > available. > ) at /usr/src/lib/librthread/rthread.c:329 > #3 0x000017d21b14e996 in _rthread_start (v=Variable "v" is not available. > ) at /usr/src/lib/librthread/rthread.c:146 > #4 0x000017d1b702268b in __tfork_thread () at > /usr/src/lib/libc/arch/amd64/sys/tfork_thread.S:75 > #5 0x0000000000000000 in ?? () >
It looks like the bootstrapper (rust-stage0/bin/rustc) may have a problem. je_tsd_cleanup come from jemalloc, and I am not sure if it is correctly build (forced to be build without thread-local-storage). another possibility is libraries vs kernel. the bootstrapper was build with: - libc.so.78.1 - libestdc++.so.16.0 - libm.so.9.0 - libpthread.so.18.1 (there are in rust-stage0/lib). In the two cases a rebuild of the bootstrapper would be required. I will take a look in this direction. > > I see that 'make update-plist' have removed '@bin' annotation on > > binaries (see pkg/PLIST-main). Is it normal ? > > This may be due to the change to the (very nice) file(1) rewrite, or it may > be some change in the produced binaries. Due to the above problem I can't > check further. > After updating /usr/ports, annotations comes back. Thanks. -- Sébastien Marie
