I could indeed reproduce that:
Stack trace of thread 3038787:
#0 0x0000556080008e0b log_file_remaining (fdupes + 0xbe0b)
#1 0x000055608000315a deletesuccessor (fdupes + 0x615a)
#2 0x0000556080000dd8 main (fdupes + 0x3dd8)
#3 0x00007f46c8255d0a __libc_start_main (libc.so.6 + 0x26d0a)
#4 0x000055608000103a _start (fdupes + 0x403a)
Let me know if I can provide more info.
Best regards,
Otto.
On 15/12/2020 16:43, Bernhard Übelacker wrote:
Hello Otto,
if you still can reproduce the segfault then it might
also be possible to install the package systemd-coredump.
That way a backtrace should show up in 'journalctl -e' giving
some more details of where the segfault happens.
This should get more informative if the fdupes-dbgsym gets
installed. This would be another repo described in [1].
Kind regards,
Bernhard
[1]
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
