public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104731] 27_io/filesystem/iterators/error_reporting.cc FAILs
Date: Thu, 22 Dec 2022 11:45:38 +0000	[thread overview]
Message-ID: <bug-104731-4-dKDlUoGkRv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104731-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104731

--- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:d176d5b3e734cac0ab1e613c3f1bbe48c0bab81a

commit r11-10434-gd176d5b3e734cac0ab1e613c3f1bbe48c0bab81a
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Nov 22 19:15:53 2022 +0000

    libstdc++: Fix unsafe use of dirent::d_name [PR107814]

    Copy the fix for PR 104731 to the equivalent experimental::filesystem
    test.

    libstdc++-v3/ChangeLog:

            PR libstdc++/107814
            * testsuite/experimental/filesystem/iterators/error_reporting.cc:
            Use a static buffer with space after it.

    (cherry picked from commit 1cac00d013856fea4cee0f13c4959c8e21afd2d9)

  parent reply	other threads:[~2022-12-22 11:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 10:40 [Bug libstdc++/104731] New: " ro at gcc dot gnu.org
2022-03-01 10:41 ` [Bug libstdc++/104731] " ro at gcc dot gnu.org
2022-03-01 12:27 ` redi at gcc dot gnu.org
2022-03-01 12:30 ` redi at gcc dot gnu.org
2022-03-01 12:33 ` redi at gcc dot gnu.org
2022-05-06  8:32 ` jakub at gcc dot gnu.org
2022-05-06 13:52 ` cvs-commit at gcc dot gnu.org
2022-05-06 13:54 ` redi at gcc dot gnu.org
2022-05-09 10:13 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-05-09 11:27 ` redi at gcc dot gnu.org
2022-05-09 11:29 ` cvs-commit at gcc dot gnu.org
2022-05-09 11:33 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-05-09 12:02 ` cvs-commit at gcc dot gnu.org
2022-05-09 12:03 ` redi at gcc dot gnu.org
2022-06-15  8:15 ` cvs-commit at gcc dot gnu.org
2022-11-23 10:20 ` cvs-commit at gcc dot gnu.org
2022-12-21 11:37 ` cvs-commit at gcc dot gnu.org
2022-12-22 11:45 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-27 20:08 ` cvs-commit at gcc dot gnu.org

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-104731-4-dKDlUoGkRv@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).