Hello Florian and Maxim, Florian Weimer <fwei...@redhat.com> writes:
> * Maxim Kuvyrkov: > >> Produces 8 regressions 1564 fixes: >> | >> | regressions.sum: >> | Running gdb:gdb.dap/cxx-exception.exp ... >> | FAIL: gdb.dap/cxx-exception.exp: exceptions in log file > > Traceback (most recent call last): > File > "/home/tcwg-buildslave/workspace/tcwg_gnu_2/abe/builds/destdir/aarch64-unknown-linux-gnu/libc/lib/libstdc++.so.6.0.34-gdb.py", > line 69, in <module> > from libstdcxx.v6 import register_libstdcxx_printers > ModuleNotFoundError: No module named 'libstdcxx' > > This may just be because the toolchain has not been ported to Debian's > multi-arch paths. > > It's possible that the previous failures obscured this problem, so it > gets reported now? This patch restores the testsuite successes and failures from before your "elf: Restore support for _r_debug interpositions and copy relocations" patch series, so everything is good. Thanks for the fix! The ModuleNotFoundError error is preexisting. It's a known problem due to how we install glibc in our CI scripts. The high number of fixes is because the patch series mentioned above had broken the ld.so breakpoint hook used by GDB to detect loading of shared libraries (which affected many testcases) and this patch fixed it. We currently build glibc without system tap probes support. I will change that. -- Thiago _______________________________________________ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
