Date: Fri, 15 Dec 2023 14:04:44 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list Message-ID: <bug-267751-29464-FJqfqXmxoO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267751-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-267751-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267751 Andreas Tobler <andreast@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andreast@FreeBSD.org --- Comment #25 from Andreas Tobler <andreast@FreeBSD.org> --- Created attachment 247061 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D247061&action= =3Dedit Possible fix for BUS error on asan init This is a possible fix for the bus error happening on gcc-13 and up when running asan tests. (Or other binaries compiled with -fsanitize=3Daddress).= I tested it with gmake check-gcc RUNTESTFLAGS=3Dasan.exp on current gcc-13 git branch. (including the patch in FindFirstDSOCallback). There are only the known swapcontext failures. As said, a possible fix. Maybe we have to investigate more in deep. But at least it is a starting point. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267751-29464-FJqfqXmxoO>