On Thu, 16 Jun 2016 at 12:06:12 -0400, Simon McVittie wrote: > I'm trying to reproduce this failure on the porterbox etler.debian.org > by rebuilding the package or by using the installed-tests from 2016.5-3.
I can reproduce it eventually, but the gdb report is unhelpful. Is there anything special that I'd need to do to get a useful backtrace on mipsel? (gdb) thread apply all bt full Thread 3 (LWP 4232): #0 0x775b697c in ?? () No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 2 (LWP 4215): #0 0x7777ec60 in ?? () No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (LWP 4231): #0 0x777d151c in ?? () No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) To reproduce: * build ostree (I used 2016.5-4) * while TEST_SKIP_CLEANUP=1 make check-TESTS TESTS=tests/test-pull-archive-z.sh; do :; done (and let it run for a while until it fails) * look for a line like "Skipping cleanup of /var/tmp/tap-test.7eaT36" in test-suite.log * ./libtool --mode=execute gdb ostree /var/tmp/tap-test.7eaT36/core I'm going to try with valgrind, and if I can't get anything useful out of that, either ignore the test failure on mipsel, or ask for the 2016.5-3 binaries to be removed so they don't block ostree migrating to testing on other architectures. S