Invalid UTF-8 (Core Dump) about dwarfs

[pfactum]

It's most definitely a weird file name and for some reason nobody has encountered this before. Congrats! :)

FWIW, I did, but I thought this was my problem, so I ran convmv on an affected folder, and this fixed it for me. I should have reported this earlier, yes :(.

[mhx]

Hi and thanks for your report.

It's most definitely a weird file name and for some reason nobody has encountered this before. Congrats! :)

I reckon some of the files originate from Windows or from a system using a non-UTF-8 locale. Given that it's just 170 files, it should be relatively easy to spot.

I can easily reproduce this here with a specially crafted file name:

$ ls tmp   
''$'\334''berraschung'
$ ./mkdwarfs -i tmp -o /dev/null --force
I 23:11:49.632683 scanning "/home/mhx/git/github/dwarfs/build-clang/tmp"
I 23:11:49.632794 assigning directory and link inodes...
I 23:11:49.632806 waiting for background scanners...
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

0 dirs, 0/0 soft/hard links, 0/0 files, 0 other
original size: 0 B, hashed: 0 B (0 files, 0 B/s)
scanned: 0 B (0 files, 0 B/s), categorizing: 0 B/s
saved by deduplication: 0 B (0 files), saved by segmenting: 0 B
filesystem: 0 B in 0 blocks (0 chunks, 0 fragments, 0/0 inodes)
compressed filesystem: 0 blocks/0 B written
▏                                                                                                                                                               ▏  0% 🌑
terminate called after throwing an instance of 'utf8::invalid_utf8'
  what():  Invalid UTF-8
*** Aborted at 1707174709 (Unix time, try 'date -d @1707174709') ***
*** Signal 6 (SIGABRT) (0x3e8000057ce) received by PID 22478 (pthread TID 0x7fb19d5ff6c0) (linux TID 22479) (maybe from PID 22478, UID 1000) (code: -6), stack trace: ***
    @ 0000000000526622 folly::symbolizer::(anonymous namespace)::signalHandler(int, siginfo_t*, void*)
                       /home/mhx/git/github/dwarfs/folly/folly/experimental/symbolizer/SignalHandler.cpp:449
    @ 00000000000397cf (unknown)
    @ 00000000000881fc (unknown)
    @ 0000000000039731 raise
    @ 00000000000224ec abort
    @ 00000000000a0c8f (unknown)
    @ 00000000000b3145 (unknown)
    @ 00000000000b31b0 std::terminate()
    @ 00000000000b33f2 __cxa_throw
    @ 0000000000519cc0 __cxa_throw
                       /home/mhx/git/github/dwarfs/folly/folly/experimental/exception_tracer/ExceptionTracerLib.cpp:159
    @ 0000000000357642 unsigned int utf8::next<char const*>(char const*&, char const*)
    @ 00000000003567ea dwarfs::utf8_display_width(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
    @ 00000000001a8d2d dwarfs::console_writer::update(dwarfs::progress&, bool)
    @ 00000000002ab25b std::thread::_State_impl<std::thread::_Invoker<std::tuple<dwarfs::progress::progress(folly::Function<void (dwarfs::progress&, bool)>&&, unsigned int)::$_0> > >::_M_run()

I'm not entirely sure about the best way to fix this yet, but it's certainly not going to take long.

[mhx]

In the meantime, a workaround is to use the --no-progress flag. This should prevent the crash.

[mhx]

Fixed in v0.9.1.