Your message dated Wed, 31 Jul 2024 15:33:15 +0800 with message-id <CALr4YMHN981n2u4oYN4rk+3BHjoOs4HEOB_UeZMZU6pa_xTQMA@mail.gmail.com> and subject line Re: Bug#1072929: cyanrip: Segmentation fault upon running `cyanrip' has caused the Debian Bug report #1072929, regarding cyanrip: Segmentation fault upon running `cyanrip' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1072929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072929 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: cyanrip: Segmentation fault upon running `cyanrip'
- From: Danai SAE-HAN (韓達耐) <danai@debian.org>
- Date: Mon, 10 Jun 2024 22:21:07 +0800
- Message-id: <171802926782.3956940.10062435085949918365.reportbug@bonbonbonbon.kalimero>
Package: cyanrip Version: 0.9.3.1-1 Severity: important Hi! When running cyanrip on an amd64 setup ("testing" mainly), I get a segmentation fault SIGSEGV(11): $ cyanrip -s 6 -N -c 1/2 -U -r 3 Checking /dev/cdrom for cdrom... CDROM sensed: TSSTcorp CDDVDW SH-224FB SB00 SCSI CD-ROM Opening drive... zsh: segmentation fault cyanrip -s 6 -N -c 1/2 -U -r 3 $ echo $? 139 When I have a look at /var/log/kern.log and syslog, I get: kernel: cyanrip[3956208]: segfault at 0 ip 00007f6a7e773647 sp 00007ffe5fe46368 error 4 in libc.so.6[7f6a7e641000+157000] likely on CPU 10 (core 2, socket 0) kernel: Code: 48 01 d0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 c4 41 01 ef ff 89 f8 09 f0 c1 e0 14 3d 00 00 00 f8 0f 87 29 03 00 00 <c5> fe 6f 07 c5 fd 74 0e c5 85 74 d0 c5 ed df c9 c5 fd d7 c9 ff c1 Running in gdb, it complains about a missing file "strcmp-avx2.S": $ gdb cyanrip Reading symbols from cyanrip... (No debugging symbols found in cyanrip) (gdb) run -s 6 -N -c 1/2 -U -r 3 Starting program: /usr/bin/cyanrip -s 6 -N -c 1/2 -U -r 3 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Checking /dev/cdrom for cdrom... CDROM sensed: TSSTcorp CDDVDW SH-224FB SB00 SCSI CD-ROM Opening drive... [New Thread 0x7fffe6e006c0 (LWP 3942446)] [Thread 0x7fffe6e006c0 (LWP 3942446) exited] Thread 1 "cyanrip" received signal SIGSEGV, Segmentation fault. __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:283 283 ../sysdeps/x86_64/multiarch/strcmp-avx2.S: No such file or directory. (gdb) bt #0 __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:283 #1 0x00005555555698b6 in () #2 0x000055555555b585 in () #3 0x00007ffff4442c8a in __libc_start_call_main (main=main@entry=0x555555559f20, argc=argc@entry=9, argv=argv@entry=0x7fffffffdbd8) at ../sysdeps/nptl/libc_start_call_main.h:58 #4 0x00007ffff4442d45 in __libc_start_main_impl (main=0x555555559f20, argc=9, argv=0x7fffffffdbd8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdbc8) at ../csu/libc-start.c:360 #5 0x000055555555d131 in () Let me know if you need more info. Cheers -- Danai -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cyanrip depends on: ii libavcodec60 7:6.1.1-4+b2 ii libavfilter9 7:6.1.1-4+b2 ii libavformat60 7:6.1.1-4+b2 ii libavutil58 7:6.1.1-4+b2 hi libc6 2.38-11 ii libcdio-cdda2t64 10.2+2.0.2-1 ii libcdio-paranoia2t64 10.2+2.0.2-1 ii libcdio19t64 2.1.0-4.2 ii libcurl4t64 8.8.0-1 ii libmusicbrainz5-2 5.1.0+git20150707-10+b1 ii libswresample4 7:6.1.1-4+b2 cyanrip recommends no packages. cyanrip suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 1072929-done@bugs.debian.org
- Cc: Bernhard Übelacker <bernhardu@mailbox.org>
- Subject: Re: Bug#1072929: cyanrip: Segmentation fault upon running `cyanrip'
- From: Danai SAE-HAN (韓達耐) <danai@debian.org>
- Date: Wed, 31 Jul 2024 15:33:15 +0800
- Message-id: <CALr4YMHN981n2u4oYN4rk+3BHjoOs4HEOB_UeZMZU6pa_xTQMA@mail.gmail.com>
- In-reply-to: <2ad3dcb3-9e96-481d-b416-b902f6da12dd@mailbox.org>
- References: <171802926782.3956940.10062435085949918365.reportbug@bonbonbonbon.kalimero> <CALr4YMFbQwiffVFFyGsxQ1xggdajHH-fja0FQBZFeuqOKZcVsA@mail.gmail.com> <CALr4YMH3kmjgbRc6ByN8hWvXruUui0tZ+jTn8qBrMoJF_iFiyg@mail.gmail.com> <2ad3dcb3-9e96-481d-b416-b902f6da12dd@mailbox.org>
Hi Bernhard,Sorry for the late reply; my newborn has upended my sleep cycle. ;-)I can't replicate the error anymore. I removed an older version of the libav package that was not in the repository anymore, and cyanrip works now.So I am closing the bug.Thanks for the pointers; I will improve my reporting next time.Cheers--DanaiOn Fri, 21 Jun 2024 at 17:40, Bernhard Übelacker <bernhardu@mailbox.org> wrote:On Thu, 13 Jun 2024 20:24:33 +0800 =?UTF-8?B?RGFuYWkgU0FFLUhBTiAo6Z+T6YGU6ICQKQ==?= <danai@debian.org> wrote:
> ==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)
> Thread 1 "cyanrip" received signal SIGSEGV, Segmentation fault.
> (gdb) bt
> #0 __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:283
> #1 0x00005555555698b6 in ()
> #2 0x000055555555b585 in ()
> #3 0x00007ffff4442c8a in __libc_start_call_main (main=main@entry=0x555555559f20, argc=argc@entry=9, argv=argv@entry=0x7fffffffdbd8) at ../sysdeps/nptl/libc_start_call_main.h:58
> #4 0x00007ffff4442d45 in __libc_start_main_impl (main=0x555555559f20, argc=9, argv=0x7fffffffdbd8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdbc8) at ../csu/libc-start.c:360
> #5 0x000055555555d131 in ()
Hello Danai,
the lines at 0x555555... are in the main executable and unfortunately your
gdb could not locate the debug symbols.
Therefore a first step would be to get these, then debuggers
should be able to show source line information.
This page lists a few ways: https://wiki.debian.org/HowToGetABacktrace
I find it nice to add the debug repository and install
the dbgsym packages as needed, in this case cyanrip-dbgsym.
The DEBUGINFOD_URLS method is easier, but may take longer because it downloads
everything for the debugged process and creates a cache directory in HOME.
Kind regards,
Bernhard
--- End Message ---