public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "laurent.alfonsi at linaro dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107940] temp_directory_path testcase broken
Date: Sat, 03 Dec 2022 21:24:16 +0000 [thread overview]
Message-ID: <bug-107940-4-l46cIZRhoB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107940-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107940
laurent.alfonsi at linaro dot org <laurent.alfonsi at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #8 from laurent.alfonsi at linaro dot org <laurent.alfonsi at linaro dot org> ---
(In reply to Andrew Pinski from comment #7)
>
> 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).
Introducing fix pointed in PR107678 well fixes the crash I am observing.
However, I m not able to ensure the problem is fully fixed. Because, The
valgrind uninit issues I was observing when building in -static are still
present. As far as i have seen, crash not exposed in -static [chance?].
I proposed to mark it as duplicate of 107678.
Thanks Andrew, Thanks Prathamesh.
*** This bug has been marked as a duplicate of bug 107678 ***
prev parent reply other threads:[~2022-12-03 21:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 20:47 [Bug libstdc++/107940] New: " laurent.alfonsi at linaro dot org
2022-11-30 22:00 ` [Bug libstdc++/107940] " redi at gcc dot gnu.org
2022-11-30 22:06 ` pinskia at gcc dot gnu.org
2022-11-30 22:29 ` redi at gcc dot gnu.org
2022-11-30 22:49 ` laurent.alfonsi at linaro dot org
2022-12-01 14:23 ` redi at gcc dot gnu.org
2022-12-01 16:50 ` laurent.alfonsi at linaro dot org
2022-12-01 19:57 ` pinskia at gcc dot gnu.org
2022-12-03 21:24 ` laurent.alfonsi at linaro dot org [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-107940-4-l46cIZRhoB@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).