diff options
| author | Tim Schumacher <timschumi@gmx.de> | 2022-12-23 14:19:42 +0100 |
|---|---|---|
| committer | Tim Flynn <trflynn89@pm.me> | 2022-12-23 10:38:14 -0500 |
| commit | 9805f73704fb54c63ae80224cf48e70ac7913d2a (patch) | |
| tree | 76b1bfdc970f7fc8bc31a9a771cb997e7d4172fb /Userland/Applications/CrashReporter/main.cpp | |
| parent | 355e761a029ab86f9cdfa4376d3e705f7457d951 (diff) | |
| download | serenity-9805f73704fb54c63ae80224cf48e70ac7913d2a.zip | |
LibCore: Remove the `force` parameter from File::remove
About half of the usages were not using `force` anyways, and the other
half presumably just got confused about what "force" really means in
this context (which is "ignore nonexistent files").
The only 'legitimate' user, which is `rm`, instead now handles this
completely internally instead.
Diffstat (limited to 'Userland/Applications/CrashReporter/main.cpp')
| -rw-r--r-- | Userland/Applications/CrashReporter/main.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Userland/Applications/CrashReporter/main.cpp b/Userland/Applications/CrashReporter/main.cpp index ae21f397ce..60783c89fd 100644 --- a/Userland/Applications/CrashReporter/main.cpp +++ b/Userland/Applications/CrashReporter/main.cpp @@ -135,7 +135,7 @@ static TitleAndText build_cpu_registers(const ELF::Core::ThreadInfo& thread_info static void unlink_coredump(StringView const& coredump_path) { - if (Core::File::remove(coredump_path, Core::File::RecursionMode::Disallowed, false).is_error()) + if (Core::File::remove(coredump_path, Core::File::RecursionMode::Disallowed).is_error()) dbgln("Failed deleting coredump file"); } |