This bug was fixed in the package gcc-13 - 13.2.0-21ubuntu1
---------------
gcc-13 (13.2.0-21ubuntu1) noble; urgency=medium
* Merge with Debian; remaining changes:
- Build from upstream sources.
gcc-13 (13.2.0-21) unstable; urgency=medium
* Update to git 20240324 from the gcc-13 branch.
- Fix PR fortran/101135, PR fortran/55978.
* Update the proposed patch to fix PR ada/114064.
* Move the _FORTIFY_SOURCE setting from cc1 to the driver.
* Refresh patches.
gcc-13 (13.2.0-20) unstable; urgency=medium
* Update to git 20240323 from the gcc-13 branch.
- Fix PR other/109668, PR tree-optimization/114231,
PR tree-optimization/112793, PR tree-optimization/113670,
PR middle-end/113622, PR tree-optimization/114203, PR middle-end/114070,
PR middle-end/114070, PR tree-optimization/114027, PR debug/112718,
PR tree-optimization/113910, PR tree-optimization/111736,
PR tree-optimization/114396, PR target/113950 (PPC),
PR target/111822 (x86), PR target/114160 (RISCV), PR sanitizer/112709,
PR sanitizer/112709, PR target/114339 (x86), PR middle-end/113907,
PR target/114310 (AArch64), PR rtl-optimization/110079,
PR rtl-optimization/114211, PR target/114184 (x86), PR fortran/114001,
PR fortran/103715, PR fortran/110826, PR fortran/100988,
PR fortran/104819, PR libstdc++/66146, PR libstdc++/114316,
PR libstdc++/114147.
* Make vhdl known to the PPC backend.
* Use the proposed patch to fix PR ada/114064, 64bit definitions for
time_t_bits type on 32bit archs.
* libsanitizer: Remove crypt and crypt_r interceptors for releases
with glibc (>= 2.31). Remove the build hacks for crypt.h.
* libstdc++-dev: Install libstdc++_libbacktrace.a. Note that all Filesystem TS
and std::stacktrace symbols were added to libstdc++exp.a and GCC 14 stops
shipping libstdc++_libbacktrace.a. Closes: #1065359.
-- Matthias Klose <d...@ubuntu.com> Sun, 24 Mar 2024 14:57:17 +0100
** Changed in: gcc-13 (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2048768
Title:
Autopkgtest failures on amd64
Status in gcc-10 package in Ubuntu:
Confirmed
Status in gcc-11 package in Ubuntu:
Confirmed
Status in gcc-12 package in Ubuntu:
Confirmed
Status in gcc-13 package in Ubuntu:
Fix Released
Status in gcc-8 package in Ubuntu:
Invalid
Status in gcc-9 package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in llvm-toolchain-14 package in Ubuntu:
Confirmed
Status in llvm-toolchain-15 package in Ubuntu:
Confirmed
Status in llvm-toolchain-16 package in Ubuntu:
Confirmed
Status in gcc-10 source package in Noble:
Confirmed
Status in gcc-11 source package in Noble:
Confirmed
Status in gcc-12 source package in Noble:
Confirmed
Status in gcc-13 source package in Noble:
Fix Released
Status in gcc-8 source package in Noble:
Invalid
Status in gcc-9 source package in Noble:
Confirmed
Status in linux source package in Noble:
Confirmed
Status in llvm-toolchain-14 source package in Noble:
Confirmed
Status in llvm-toolchain-15 source package in Noble:
Confirmed
Status in llvm-toolchain-16 source package in Noble:
Confirmed
Bug description:
Some tests related to the address sanitizer are occasionally failing
on amd64 (also for llvm-toolchain-15 and 16):
--------------
FAIL: LLVM regression suite :: test_leaksan.c (38 of 45)
746s ******************** TEST 'LLVM regression suite :: test_leaksan.c'
FAILED ********************
746s Script:
746s --
746s : 'RUN: at line 4'; /usr/bin/clang-14 -o
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp
-fsanitize=address -g
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c
746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0"
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp
2>&1 >
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
746s : 'RUN: at line 6'; grep -q "detected memory leaks"
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
746s --
746s Exit Code: 139
746s
746s Command Output (stderr):
746s --
746s
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script:
line 3: 3335 Segmentation fault (core dumped) env
ASAN_OPTIONS="log_path=stdout:exitcode=0"
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp
2>&1 >
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
--------------
If you run the test manually you'll notice that it works but
eventually crashes:
--------------------
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$
./test_leaksan.c.tmp
=================================================================
==8631==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 7 byte(s) in 1 object(s) allocated from:
#0 0x5e9c3441ed12 in __interceptor_malloc
(/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12)
(BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193)
#1 0x5e9c3445acb8 in main
/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7
#2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId:
f0b834daa3d05a80967e9ec2f990a1ea71c958fa)
SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s).
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$
./test_leaksan.c.tmp
=================================================================
==8634==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 7 byte(s) in 1 object(s) allocated from:
#0 0x5f19be5f6d12 in __interceptor_malloc
(/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12)
(BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193)
#1 0x5f19be632cb8 in main
/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7
#2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId:
f0b834daa3d05a80967e9ec2f990a1ea71c958fa)
SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s).
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$
./test_leaksan.c.tmp
Segmentation fault (core dumped)
--------------------
After some investigation I found that it will not fail with ASLR
disabled:
sudo sysctl kernel.randomize_va_space=0
while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0"
./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ;
fi done
If you enable ASLR it will start to crash:
$ sudo sysctl kernel.randomize_va_space=2
$ while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0"
./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done
Segmentation fault (core dumped)
crashed
Segmentation fault (core dumped)
crashed
Segmentation fault (core dumped)
crashed
Segmentation fault (core dumped)
crashed
Segmentation fault (core dumped)
crashed
If you enable ASLR again and run it with "setarch -R" (to disable ASLR
for this binary), it will also not crash.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/2048768/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
