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++/99533] "operation not permitted" error on recursive_directory_iterator despite skip_permission_denied Date: Mon, 29 Mar 2021 20:03:22 +0000 [thread overview] Message-ID: <bug-99533-4-cycIBqFO6o@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99533-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99533 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:6e5f662f1dd6e3d1a79e194c118c295b897fc7ef commit r10-9593-g6e5f662f1dd6e3d1a79e194c118c295b897fc7ef Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Mar 11 16:43:51 2021 +0000 libstdc++: Handle EPERM for filesystem access errors on MacOS [PR 99537] Contrary to what POSIX says, some directory operations on MacOS can fail with EPERM instead of EACCES, so we need to handle both. libstdc++-v3/ChangeLog: PR libstdc++/99533 * src/c++17/fs_dir.cc (recursive_directory_iterator): Use new helper function to check for permission denied errors. * src/filesystem/dir.cc (recursive_directory_iterator): Likewise. * src/filesystem/dir-common.h (is_permission_denied_error): New helper function. (cherry picked from commit 8cfb387388a90730ab36ac24d9049677db633a11)
next prev parent reply other threads:[~2021-03-29 20:03 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-10 23:04 [Bug libstdc++/99533] New: " ssh at pobox dot com 2021-03-11 13:12 ` [Bug libstdc++/99533] " redi at gcc dot gnu.org 2021-03-11 13:15 ` redi at gcc dot gnu.org 2021-03-11 15:06 ` redi at gcc dot gnu.org 2021-03-11 18:21 ` redi at gcc dot gnu.org 2021-03-14 7:05 ` ssh at pobox dot com 2021-03-29 20:03 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-29 21:37 ` redi at gcc dot gnu.org 2021-04-20 18:52 ` cvs-commit at gcc dot gnu.org 2021-04-20 18:53 ` redi at gcc dot gnu.org 2022-12-19 21:55 ` redi 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-99533-4-cycIBqFO6o@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: linkBe 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).