If it's any help, here is the output from Valgrind:
valgrind --leak-check=full cyanrip -s 6 -N -c 1/2 -U -r 3
==659486== Memcheck, a memory error detector
==659486== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==659486== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info
==659486== Command: cyanrip -s 6 -N -c 1/2 -U -r 3
==659486==
Checking /dev/cdrom for cdrom...
CDROM sensed: TSSTcorp CDDVDW SH-224FB SB00 SCSI CD-ROM
Opening drive...
==659486== Warning: noted but unhandled ioctl 0x5325 with no size/direction hints.
==659486== This could cause spurious value errors to appear.
==659486== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper.
==659486== Invalid read of size 1
==659486== at 0x4847DC4: strcmp (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==659486== by 0x11D8A5: ??? (in /usr/bin/cyanrip)
==659486== by 0x10F57C: ??? (in /usr/bin/cyanrip)
==659486== by 0x8100C89: (below main) (libc_start_call_main.h:58)
==659486== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==659486==
==659486==
==659486== Process terminating with default action of signal 11 (SIGSEGV)
==659486== Access not within mapped region at address 0x0
==659486== at 0x4847DC4: strcmp (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==659486== by 0x11D8A5: ??? (in /usr/bin/cyanrip)
==659486== by 0x10F57C: ??? (in /usr/bin/cyanrip)
==659486== by 0x8100C89: (below main) (libc_start_call_main.h:58)
==659486== If you believe this happened as a result of a stack
==659486== overflow in your program's main thread (unlikely but
==659486== possible), you can try to increase the size of the
==659486== main thread stack using the --main-stacksize= flag.
==659486== The main thread stack size used in this run was 8388608.
==659486==
==659486== HEAP SUMMARY:
==659486== in use at exit: 13,140,444 bytes in 3,166 blocks
==659486== total heap usage: 5,891 allocs, 2,725 frees, 13,565,769 bytes allocated
==659486==
==659486== 640 bytes in 1 blocks are possibly lost in loss record 936 of 994
==659486== at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==659486== by 0x40112A2: calloc (rtld-malloc.h:44)
Is this an upstream issue, or a Debian-specific issue? If the former, let me know so I can raise it on Github.
Thanks and regards.
--
Danai