public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpie@msc-ge.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/105422] New: filesystem::copy does not throw exceptions when a subdirectory exists
Date: Thu, 28 Apr 2022 13:26:36 +0000	[thread overview]
Message-ID: <bug-105422-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105422
           Summary: filesystem::copy does not throw exceptions when a
                    subdirectory exists
           Product: gcc
           Version: 11.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mpie@msc-ge.com
  Target Milestone: ---

Created attachment 52895
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52895&action=edit
Example file to reproduce behaviour

Hi,

in Ubuntu 21.10 a recursive filesystem::copy() does correctly throw an
exception if a file can't be read. But it will not throw an exception if there
is an empty subdirectory. The destination will therefore miss a file without a
report. Also the error code will be empty.

See the output of the attached copy_bug.cpp

$ c++ copy_bug.cpp -o copy_bug --std=c++17
$ ./copy_bug

Copytest with withSubDir=0
Exception: filesystem error: cannot copy: Permission denied [test/source]
[test/dest]
Error code: Permission denied
Copytest with withSubDir=1

$ tree -p test       
test
├── [drwxrwxr-x]  dest
│   └── [drwxrwxr-x]  subdir
├── [drwxrwxr-x]  dest_ec
│   └── [drwxrwxr-x]  subdir
└── [drwxrwxr-x]  source
    ├── [drwxrwxr-x]  subdir
    └── [----------]  test.txt

             reply	other threads:[~2022-04-28 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 13:26 mpie@msc-ge.com [this message]
2022-04-28 13:31 ` [Bug libstdc++/105422] " 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-105422-4@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).