> On 23 Feb 2016, at 09:26, David Abdurachmanov <[email protected]> > wrote: > > It would be nice to test on Fedora Rawhide as it has GCC 6.0.0 and glibc 2.23.
## Fedora Rawhide (pre-24) + x86_64 http://davidlt.web.cern.ch/davidlt/vault/libunwind/fedora_rawhide_x86_64.log // make check http://davidlt.web.cern.ch/davidlt/vault/libunwind/test-suite_fedora_rawhide_x86_64.log # gcc -dumpversion 6.0.0 # ld -version GNU ld version 2.26.20160125 # /lib64/libc.so.6 GNU C Library (GNU libc) development release version 2.22.90, by Roland McGrath et al. ============================================================================ Testsuite summary for libunwind 1.1 ============================================================================ # TOTAL: 33 # PASS: 30 # SKIP: 0 # XFAIL: 2 # FAIL: 1 # XPASS: 0 # ERROR: 0 lt-test-coredump-unwind: _UCD_create('/tmp/libunwind-test-kZwbBv0XnO/core*') failed On systemd based distributions there is a high probability that core dump will be here: $ cat /proc/sys/kernel/core_pattern |/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e $ find /var/lib/systemd/coredump /var/lib/systemd/coredump /var/lib/systemd/coredump/core.crasher.1000.e8ae95b26f4a420a9b7685b3dc5e0b8a.11136.1456215688000000.xz /var/lib/systemd/coredump/core.crasher.1000.e8ae95b26f4a420a9b7685b3dc5e0b8a.19289.1456061204000000.xz I think, one could improve test case to handle various /proc/sys/kernel/core_pattern patterns. We can look for core dump based on "crasher" process name and PID, then copy (uncompressed) to expected location. This would be nice to improve to help package maintainers. I might come up with some patch, but not this week. david _______________________________________________ Libunwind-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/libunwind-devel
