Your message dated Mon, 22 Feb 2016 14:36:03 +0100
with message-id <8883545.dqvHHLnpKu@localhost>
and subject line Re: rustc: FTBFS on i386:
run-pass-valgrind/down-with-thread-dtors.rs ... FAILED
has caused the Debian Bug report #812825,
regarding rustc: FTBFS on i386: run-pass-valgrind/down-with-thread-dtors.rs ...
FAILED
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
812825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rustc
Version: 1.6.0+dfsg1-2
Severity: serious
Justification: fails to build from source
rustc compilation succeeds again on i386 now that you've taken care of
#812448. (Thanks!) However, the build still eventually fails, with a
test suite error, as detailed below. Could you please take a look?
Thanks!
https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=i386&ver=1.6.0%2Bdfsg1-2&stamp=1453812219
test [run-pass-valgrind] run-pass-valgrind/down-with-thread-dtors.rs ... FAILED
[...]
failures:
---- [run-pass-valgrind] run-pass-valgrind/down-with-thread-dtors.rs stdout ----
error: test run failed!
status: signal: 9
command: /usr/bin/valgrind --error-exitcode=100 --fair-sched=try --quiet
--soname-synonyms=somalloc=NONE
--suppressions=/«BUILDDIR»/rustc-1.6.0+dfsg1/src/etc/x86.supp --tool=memcheck
--leak-check=full
i686-unknown-linux-gnu/test/run-pass-valgrind/down-with-thread-dtors.stage2-i686-unknown-linux-gnu
stdout:
------------------------------------------
------------------------------------------
stderr:
------------------------------------------
--29164-- WARNING: Serious error when reading debug info
--29164-- When reading debug info from /lib/i386-linux-gnu/ld-2.21.so:
--29164-- Ignoring non-Dwarf2/3/4 block in .debug_info
--29164-- WARNING: Serious error when reading debug info
--29164-- When reading debug info from /lib/i386-linux-gnu/ld-2.21.so:
--29164-- Last block truncated in .debug_info; ignoring
--29164-- WARNING: Serious error when reading debug info
--29164-- When reading debug info from /lib/i386-linux-gnu/ld-2.21.so:
--29164-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--29164-- WARNING: Serious error when reading debug info
--29164-- When reading debug info from /lib/i386-linux-gnu/libc-2.21.so:
--29164-- Ignoring non-Dwarf2/3/4 block in .debug_info
--29164-- WARNING: Serious error when reading debug info
--29164-- When reading debug info from /lib/i386-linux-gnu/libc-2.21.so:
--29164-- Last block truncated in .debug_info; ignoring
--29164-- WARNING: Serious error when reading debug info
--29164-- When reading debug info from /lib/i386-linux-gnu/libc-2.21.so:
--29164-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--29164-- WARNING: Serious error when reading debug info
--29164-- When reading debug info from /lib/i386-linux-gnu/libdl-2.21.so:
--29164-- Ignoring non-Dwarf2/3/4 block in .debug_info
--29164-- WARNING: Serious error when reading debug info
--29164-- When reading debug info from /lib/i386-linux-gnu/libdl-2.21.so:
--29164-- Last block truncated in .debug_info; ignoring
--29164-- WARNING: Serious error when reading debug info
--29164-- When reading debug info from /lib/i386-linux-gnu/libdl-2.21.so:
--29164-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--29164-- WARNING: Serious error when reading debug info
--29164-- When reading debug info from /lib/i386-linux-gnu/libm-2.21.so:
--29164-- Ignoring non-Dwarf2/3/4 block in .debug_info
--29164-- WARNING: Serious error when reading debug info
--29164-- When reading debug info from /lib/i386-linux-gnu/libm-2.21.so:
--29164-- Last block truncated in .debug_info; ignoring
--29164-- WARNING: Serious error when reading debug info
--29164-- When reading debug info from /lib/i386-linux-gnu/libm-2.21.so:
--29164-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
==29164== Can't extend stack to 0x4b76880 during signal delivery for thread 2:
==29164== no stack segment
==29164==
==29164== Process terminating with default action of signal 11 (SIGSEGV)
==29164== Access not within mapped region at address 0x4B76880
==29164== at 0x109312: Bar::drop.3572::he1906ad0926bab78 (in
/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/test/run-pass-valgrind/down-with-thread-dtors.stage2-i686-unknown-linux-gnu)
==29164== by 0x4BDEA3B: __call_tls_dtors (in
/lib/i386-linux-gnu/libc-2.21.so)
==29164== by 0x4B7CF78: start_thread (pthread_create.c:343)
==29164== by 0x4C83C5D: clone (in /lib/i386-linux-gnu/libc-2.21.so)
==29164== If you believe this happened as a result of a stack
==29164== overflow in your program's main thread (unlikely but
==29164== possible), you can try to increase the size of the
==29164== main thread stack using the --main-stacksize= flag.
==29164== The main thread stack size used in this run was 8388608.
==29164== 152 bytes in 1 blocks are possibly lost in loss record 6 of 7
==29164== at 0x482E118: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==29164== by 0x4010B06: allocate_dtv (in /lib/i386-linux-gnu/ld-2.21.so)
==29164== by 0x40114EB: _dl_allocate_tls (in /lib/i386-linux-gnu/ld-2.21.so)
==29164== by 0x4B7D7B4: allocate_stack (allocatestack.c:587)
==29164== by 0x4B7D7B4: pthread_create@@GLIBC_2.1 (pthread_create.c:537)
==29164== by 0x48D3910:
sys::thread::_$LT$impl$GT$::new::h0c26d6244eb55dc5V2w (in
/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/stage2/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-ca9f0d77.so)
==29164== by 0x1096C9: main::hc93605d64ae12a98Afa (in
/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/test/run-pass-valgrind/down-with-thread-dtors.stage2-i686-unknown-linux-gnu)
==29164== by 0x48E53AA:
sys_common::unwind::try::try_fn::h10146374067150597859 (in
/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/stage2/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-ca9f0d77.so)
==29164== by 0x48DBB34: __rust_try (in
/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/stage2/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-ca9f0d77.so)
==29164== by 0x48E5037: rt::lang_start::h5844a0ea8375068ck5x (in
/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/stage2/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-ca9f0d77.so)
==29164== by 0x10A7CD: main (in
/«BUILDDIR»/rustc-1.6.0+dfsg1/i686-unknown-linux-gnu/test/run-pass-valgrind/down-with-thread-dtors.stage2-i686-unknown-linux-gnu)
==29164==
------------------------------------------
thread '[run-pass-valgrind] run-pass-valgrind/down-with-thread-dtors.rs'
panicked at 'explicit panic',
/«BUILDDIR»/rustc-1.6.0+dfsg1/src/compiletest/runtest.rs:1507
failures:
[run-pass-valgrind] run-pass-valgrind/down-with-thread-dtors.rs
test result: FAILED. 7 passed; 1 failed; 0 ignored; 0 measured
thread '<main>' panicked at 'Some tests failed',
/«BUILDDIR»/rustc-1.6.0+dfsg1/src/compiletest/compiletest.rs:244
/«BUILDDIR»/rustc-1.6.0+dfsg1/mk/tests.mk:767: recipe for target
'tmp/check-stage2-T-i686-unknown-linux-gnu-H-i686-unknown-linux-gnu-rpass-valgrind.ok'
failed
make[2]: ***
[tmp/check-stage2-T-i686-unknown-linux-gnu-H-i686-unknown-linux-gnu-rpass-valgrind.ok]
Error 101
--- End Message ---
--- Begin Message ---
Version: 1.6.0+dfsg1-3
> On Tue, 26 Jan 2016 18:52:53 -0500 "Aaron M. Ucko" <u...@debian.org> wrote:
> > rustc compilation succeeds again on i386 now that you've taken care of
> > #812448. (Thanks!) However, the build still eventually fails, with a
> > test suite error, as detailed below. Could you please take a look?
Some misbehavior in valgrind. Upstream moved the test to static linking and
this disappeared.
Cheers, Luca
--
.''`. ** Debian GNU/Linux ** | Luca Bruno (kaeso)
: :' : The Universal O.S. | lucab (AT) debian.org
`. `'` | GPG: 0xBB1A3A854F3BBEBF
`- http://www.debian.org | Debian GNU/Linux Developer
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
