Package: gcc-14 Version: 14.2.0-17 Severity: serious Justification: breaks autopkgtest of unrelated package X-Debbugs-Cc: debian-glibc@lists.debian.org, debian-...@lists.debian.org Control: affects -1 src:glibc Control: affects -1 src:libinsane
Hi, When glibc is compiled with gcc-14 >= 14.2.0-18, the libinsane autopkgtest fails on armhf [1]: | 207s autopkgtest [07:54:23]: test workaround-one-page-flatbed: [----------------------- | 207s Building | 208s Reducing file descriptors limit | 208s Running test with valgrind | 208s ==6914== Memcheck, a memory error detector | 208s ==6914== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. | 208s ==6914== Using Valgrind-3.24.0 and LibVEX; rerun with -h for copyright info | 208s ==6914== Command: /tmp/autopkgtest-lxc.6v7pbw_c/downtmp/autopkgtest_tmp/tests_workaround_one_page_flatbed | 208s ==6914== | 208s | 208s | 208s CUnit - A unit testing framework for C - Version 2.1-3 | 208s http://cunit.sourceforge.net/ | 208s | 208s | 208s Suite: Workaround_one_page_flatbed | 209s Test: tests_one_page_flatbed() ...==6914== Source and destination overlap in memcpy(0x6debcf0, 0x6debcf1, 5) | 209s ==6914== at 0x4881648: memcpy (in /usr/libexec/valgrind/vgpreload_memcheck-arm-linux.so) | 209s ==6914== | 209s passed | 209s | 209s Run Summary: Type Total Ran Passed Failed Inactive | 209s suites 1 1 n/a 0 0 | 209s tests 1 1 1 0 0 | 209s asserts 30 30 30 0 n/a | 209s | 209s Elapsed time = 0.111 seconds | 209s ==6914== | 209s ==6914== HEAP SUMMARY: | 209s ==6914== in use at exit: 0 bytes in 0 blocks | 209s ==6914== total heap usage: 292 allocs, 292 frees, 41,951 bytes allocated | 209s ==6914== | 209s ==6914== All heap blocks were freed -- no leaks are possible | 209s ==6914== | 209s ==6914== For lists of detected and suppressed errors, rerun with: -s | 209s ==6914== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 1021 from 69) | 209s autopkgtest [07:54:25]: test workaround-one-page-flatbed: -----------------------] This is fully reproducible when glibc 2.41-6 is built with gcc-14 14.2.0-18 or 14.2.0-19. On the contrary the problem disappears when rebuilding glibc 2.41-6 with gcc-14 14.2.0-17 currently in testing. In turn this prevent glibc 2.41-6 to migrate to testing. Please revert. Regards Aurelien [1] https://ci.debian.net/packages/libi/libinsane/testing/armhf/58878994/#S57
