[Pkg-rust-maintainers] Bug#812825: rustc: FTBFS on i386: run-pass-valgrind/down-with-thread-dtors.rs ... FAILED
Ximin Luo
infinity0 at debian.org
Wed Feb 10 11:03:20 UTC 2016
On Tue, 26 Jan 2016 18:52:53 -0500 "Aaron M. Ucko" <ucko at 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?
>
Similar problem on ubuntu i386 xenial, even though the amd64 build works:
https://launchpadlibrarian.net/237711068/buildlog_ubuntu-xenial-i386.rustc_1.8.0~~nightly.20160209+dfsg1-1_BUILDING.txt.gz
failures:
---- [run-pass-valgrind] run-pass-valgrind/down-with-thread-dtors.rs stdout ----
thread '<main>
' panicked at 'Some tests failed', /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/src/compiletest/compiletest.rs:
244
stack backtrace:
executing i686-unknown-linux-gnu/stage2/bin/rustc /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/src/test/run-pass-valgrind/down-with-thread-dtors.rs -L i686-unknown-linux-gnu/test/run-pass-valgrind/ --target=i686-unknown-linux-gnu -L i686-unknown-linux-gnu/test/run-pass-valgrind/down-with-thread-dtors.stage2-i686-unknown-linux-gnu.run-pass-valgrind.libaux -C prefer-dynamic -o i686-unknown-linux-gnu/test/run-pass-valgrind/down-with-thread-dtors.stage2-i686-unknown-linux-gnu -C link-args=-Wl,-Bsymbolic-functions -C link-args=-Wl,-z,relro --cfg rtopt -C rpath -O -L i686-unknown-linux-gnu/rt
------stdout------------------------------
------stderr------------------------------
1: 0xf7406984 - ------------------------------------------
sys::backtrace::executing /usr/bin/valgrind --error-exitcode=100 --fair-sched=try --quiet --soname-synonyms=somalloc=NONE --suppressions=/«BUILDDIR»/rustc-1.8.0~~nightly.20160209+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
tracing::imp::write::h59a57150de078a41Btu
------stdout------------------------------
2: 0xf740f0c1 - ------stderr------------------------------
panicking::default_handler::_$u7b$$u7b$closure$u7d$$u7d$==14154== Can't extend stack to 0x4baa880 during signal delivery for thread 2:
::closure.43171
==14154== no stack segment
3: 0xf740ec42 - ==14154==
panicking::default_handler::he7b491197c6c99803Wy
==14154== Process terminating with default action of signal 11 (SIGSEGV)
4: ==14154== Access not within mapped region at address 0x4BAA880
0xf73d36b5 - sys_common::unwind::begin_unwind_inner==14154== at 0x10937F: Bar::drop.4343::hb6fc05b24a038bcb (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/test/run-pass-valgrind/down-with-thread-dtors.stage2-i686-unknown-linux-gnu)
::h0ac7a886eb1f5e41qit
==14154== by 0x4C19245: __call_tls_dtors (cxa_thread_atexit_impl.c:88)
5: 0xf7772301 - sys_common::==14154== by 0x4BB4197: start_thread (pthread_create.c:343)
unwind::begin_unwind::h9046235623656897439
==14154== by 0x4CD400D: clone (clone.S:122)
6: 0xf776b4af==14154== If you believe this happened as a result of a stack
- main::hf00d4db88af659a1GBd
==14154== overflow in your program's main thread (unlikely but
==14154== possible), you can try to increase the size of the
7: 0xf740e6ba - sys_common::==14154== main thread stack using the --main-stacksize= flag.
unwind::try::try_fn::h7724830446344512684
==14154== The main thread stack size used in this run was 8388608.
8==14154== 296 bytes in 1 blocks are possibly lost in loss record 6 of 7
: 0xf7404287 - __rust_try
==14154== at 0x482F0D8: calloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
9: ==14154== by 0x40110F6: allocate_dtv (dl-tls.c:322)
0xf740e38c - rt::lang_start::hb58bd81a27354c059Oy==14154== by 0x4011A8B: _dl_allocate_tls (dl-tls.c:544)
==14154== by 0x4BB49FC: allocate_stack (allocatestack.c:588)
10: 0xf777235d - main==14154== by 0x4BB49FC: pthread_create@@GLIBC_2.1 (pthread_create.c:537)
==14154== by 0x48E20E3: sys::thread::Thread::new::h307134d2d360eab0UMx (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/stage2/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-fd663c41.so)
==14154== by 0x1096E0: main::h9647345f5ef49bcdGfa (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/test/run-pass-valgrind/down-with-thread-dtors.stage2-i686-unknown-linux-gnu)
11: 0xf718c71d - __libc_start_main
==14154== by 0x48F46BA: sys_common::unwind::try::try_fn::h1092320641588954410 (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/stage2/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-fd663c41.so)
==14154== by 0x48EA287: __rust_try (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/stage2/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-fd663c41.so)
12: 0xf7765d10 - <unknown>
==14154== by 0x48F438C: rt::lang_start::hb58bd81a27354c059Oy (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/stage2/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-fd663c41.so)
==14154== by 0x10A53D: main (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/test/run-pass-valgrind/down-with-thread-dtors.stage2-i686-unknown-linux-gnu)
==14154==
------------------------------------------
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.8.0~~nightly.20160209+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:
------------------------------------------
==14154== Can't extend stack to 0x4baa880 during signal delivery for thread 2:
==14154== no stack segment
==14154==
==14154== Process terminating with default action of signal 11 (SIGSEGV)
==14154== Access not within mapped region at address 0x4BAA880
==14154== at 0x10937F: Bar::drop.4343::hb6fc05b24a038bcb (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/test/run-pass-valgrind/down-with-thread-dtors.stage2-i686-unknown-linux-gnu)
==14154== by 0x4C19245: __call_tls_dtors (cxa_thread_atexit_impl.c:88)
==14154== by 0x4BB4197: start_thread (pthread_create.c:343)
==14154== by 0x4CD400D: clone (clone.S:122)
==14154== If you believe this happened as a result of a stack
==14154== overflow in your program's main thread (unlikely but
==14154== possible), you can try to increase the size of the
==14154== main thread stack using the --main-stacksize= flag.
==14154== The main thread stack size used in this run was 8388608.
==14154== 296 bytes in 1 blocks are possibly lost in loss record 6 of 7
==14154== at 0x482F0D8: calloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==14154== by 0x40110F6: allocate_dtv (dl-tls.c:322)
==14154== by 0x4011A8B: _dl_allocate_tls (dl-tls.c:544)
==14154== by 0x4BB49FC: allocate_stack (allocatestack.c:588)
==14154== by 0x4BB49FC: pthread_create@@GLIBC_2.1 (pthread_create.c:537)
==14154== by 0x48E20E3: sys::thread::Thread::new::h307134d2d360eab0UMx (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/stage2/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-fd663c41.so)
==14154== by 0x1096E0: main::h9647345f5ef49bcdGfa (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/test/run-pass-valgrind/down-with-thread-dtors.stage2-i686-unknown-linux-gnu)
==14154== by 0x48F46BA: sys_common::unwind::try::try_fn::h1092320641588954410 (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/stage2/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-fd663c41.so)
==14154== by 0x48EA287: __rust_try (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/stage2/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-fd663c41.so)
==14154== by 0x48F438C: rt::lang_start::hb58bd81a27354c059Oy (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/stage2/lib/rustlib/i686-unknown-linux-gnu/lib/libstd-fd663c41.so)
==14154== by 0x10A53D: main (in /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/i686-unknown-linux-gnu/test/run-pass-valgrind/down-with-thread-dtors.stage2-i686-unknown-linux-gnu)
==14154==
------------------------------------------
thread '[run-pass-valgrind] run-pass-valgrind/down-with-thread-dtors.rs' panicked at 'explicit panic', /«BUILDDIR»/rustc-1.8.0~~nightly.20160209+dfsg1/src/compiletest/runtest.rs:1527
stack backtrace:
1: 0xf7406984 - sys::backtrace::tracing::imp::write::h59a57150de078a41Btu
2: 0xf740f0c1 - panicking::default_handler::_$u7b$$u7b$closure$u7d$$u7d$::closure.43171
3: 0xf740eb9e - panicking::default_handler::he7b491197c6c99803Wy
4: 0xf73d36b5 - sys_common::unwind::begin_unwind_inner::h0ac7a886eb1f5e41qit
5: 0xf7772301 - sys_common::unwind::begin_unwind::h9046235623656897439
6: 0xf778cc0a - runtest::fatal_proc_rec::h5930e0c5d75b4835GIc
7: 0xf777718c - runtest::run::h20aa392944eaf978aMa
8: 0xf777bf8f - boxed::F.FnBox<A>::call_box::h4607800461995761141
9: 0xf770bc85 - sys_common::unwind::try::try_fn::h15688100237798803366
10: 0xf7404287 - __rust_try
11: 0xf73fbac6 - sys_common::unwind::inner_try::h3b9f934390263c0csft
12: 0xf770c023 - boxed::F.FnBox<A>::call_box::h2818648712924613863
13: 0xf740d57b - sys::thread::Thread::new::thread_start::h958548fa35e9aaa1nUx
14: 0xf7127189 - start_thread
15: 0xf725e00d - clone
16: 0x0 - <unknown>
failures:
[run-pass-valgrind] run-pass-valgrind/down-with-thread-dtors.rs
test result: FAILED. 7 passed; 1 failed; 0 ignored; 0 measured
--
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
git://github.com/infinity0/pubkeys.git
More information about the Pkg-rust-maintainers
mailing list