From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 38FD03858D32; Thu, 1 Dec 2022 19:57:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 38FD03858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1669924652; bh=DRIqR7dHH4bbvqPR4SpOaMlQ7L/759ZjtlMtzcgS7xA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=VLAuamJklGdr4Nq6bSa9vDu24vgTzwJTZoV4jfEUcMafJ/b2egRFJ67ZiwH80DWlX YfhFST4ySTzARIkoHpyWcCMOBw7PcAl85WEG+WGYP1Ouo20MRPyVSnY8DSDOk4A7AP q8GTWrYG2ZpUE+F74eg8lT0lM3MXjohTE9zC7dp0= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/107940] temp_directory_path testcase broken Date: Thu, 01 Dec 2022 19:57:32 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107940 --- Comment #7 from Andrew Pinski --- (In reply to laurent.alfonsi@linaro.org from comment #0) > sanitizer=3Daddress reports an issue while stack unwinding : >=20 > =3D=3D13419=3D=3DERROR: AddressSanitizer: SEGV on unknown address 0x0= 00000000000 > (pc 0x0055012adf14 bp 0x0055007ff090 sp 0x0055007ff090 T0) > =3D=3D13419=3D=3DThe signal is caused by a UNKNOWN memory access. > =3D=3D13419=3D=3DHint: address points to the zero page. The uninitialized memory dealing with the stack unwinding is recorded as PR 107678 and a patch was sent here: https://gcc.gnu.org/pipermail/gcc-patches/2022-December/607668.html (maybe = that will fix the issue recorded here too).=