From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 125CE3858D1E; Wed, 30 Nov 2022 22:00:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 125CE3858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1669845643; bh=lnhsJy9QEjBIDfCCGn6RpBZqE1HvzawyrkV6qYPHfj4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=AAXkNeQsNphVEDfwFw2mGfNUCC9nA/X+NkXWxMT8XumBDi1W2aljgCIrJhdRZk2d/ yVYXj2ipNyNWmVws/+IXiugSv8Vt9gOA/BlncYzQWWyWJybkrUIu2t5ebm8u01fwus 8TTOiQCDT6Ntlo538btQDWfGvr4ChNIrSNBHPs0U= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/107940] temp_directory_path testcase broken Date: Wed, 30 Nov 2022 22:00:42 +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: redi 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 #1 from Jonathan Wakely --- (In reply to laurent.alfonsi@linaro.org from comment #0) > This may be linked to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D9078= 7. > But, I confirm my toolchain is based on trunk (13.0), and contains the 90= 787 > fix. No, I don't think it's related to that in any way. valgrind and asan are both clean when running that test on x86_64-pc-linux-= gnu. Where does valgrind say there are uninitialized values? Maybe the problem i= s in the unwinder.=