public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ssh at pobox dot com" <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: Sun, 14 Mar 2021 07:05:59 +0000	[thread overview]
Message-ID: <bug-99533-4-gYf5l5lvEa@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 #5 from Steffen Schuemann <ssh at pobox dot com> ---
Thank you for looking into this and sorry for the namespace issue, I was to
greedy when deleting the preprocessor parts that switched between my
implementation and std::filesystem.

First of all, I'm with you in thinking the macOS issue is more of an os
problem, but knowing the chances that this gets fixed on Apples side,
especially for anything older than Big Sur, I hoped that a fix/workaround on
GCC/LLVM side would be a much better chance. Thanks for the changes, I'll try
to test macOS later this day. 

And thank you for pointing out that the situation under Linux is in fact not
the same. You are right. Sadly I was fooled to believe it is, while comparing
the behavior with my implementation but after some debugging the reason mine
iterates through /proc/1/task/1/cwd without an error is actually a bug on my
side. So I have to thank you for helping me find that one.

So to recap: EPERM issue is indeed macOS only, not Linux!

  parent reply	other threads:[~2021-03-14  7:06 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 [this message]
2021-03-29 20:03 ` cvs-commit at gcc dot gnu.org
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-gYf5l5lvEa@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).