Source: gcc-10 Version: 10.1.0-6 Tags: patch User: helm...@debian.org Usertags: rebootstrap
gcc-10 does not yet strictly validate symbols. It only does so when building cross compilers. While doing so, an architecture-specific issue regarding asan vfork symbols surfaced. The relevant symbols are listed universally, but are actually only available for some architectures. I'm attaching a patch to fix the symbols file to reflect that. The arch selector closely matches the ASAN_INTERCEPT_VFORK macro. Helmut
diff --minimal -Nru gcc-10-10.1.0/debian/changelog gcc-10-10.1.0/debian/changelog --- gcc-10-10.1.0/debian/changelog 2020-07-14 12:07:51.000000000 +0200 +++ gcc-10-10.1.0/debian/changelog 2020-07-18 06:42:14.000000000 +0200 @@ -1,3 +1,10 @@ +gcc-10 (10.1.0-6.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix ASAN_INTERCEPT_VFORK related symbols. (Closes: #-1) + + -- Helmut Grohne <hel...@subdivi.de> Sat, 18 Jul 2020 06:42:14 +0200 + gcc-10 (10.1.0-6) unstable; urgency=medium * Update to git 20200714 from the gcc-10 branch. diff --minimal -Nru gcc-10-10.1.0/debian/libasan.symbols.common gcc-10-10.1.0/debian/libasan.symbols.common --- gcc-10-10.1.0/debian/libasan.symbols.common 2020-05-02 14:18:13.000000000 +0200 +++ gcc-10-10.1.0/debian/libasan.symbols.common 2020-07-18 06:41:15.000000000 +0200 @@ -600,7 +600,7 @@ __interceptor_ttyname_r@Base 7 __interceptor_valloc@Base 4.8 __interceptor_vasprintf@Base 5 - __interceptor_vfork@Base 10 + (arch=any-armel any-armhf any-arm64 any-i386 any-amd64)__interceptor_vfork@Base 10 __interceptor_vfprintf@Base 5 __interceptor_vfscanf@Base 4.8 __interceptor_vprintf@Base 5 @@ -1764,7 +1764,7 @@ ttyname_r@Base 7 valloc@Base 4.8 vasprintf@Base 5 - vfork@Base 10 + (arch=any-armel any-armhf any-arm64 any-i386 any-amd64)vfork@Base 10 vfprintf@Base 5 vfscanf@Base 4.8 vprintf@Base 5