Re: [Cin] *** stack smashing detected ***: terminated
oh, this one looks tricky! May be adding " -fstack-protector-strong" or -fstack-protector-all" to normal build CFLAGS will uncover it on other distros? But debugging even in simple case looks time consuming: https://wiki.gentoo.org/wiki/Stack_smashing_debugging_guide пн, 1 мая 2023 г., 00:35 Stefan de Konink : > [Thread 0x7ffb70db66c0 (LWP 715673) exited] > *** stack smashing detected ***: terminated > > Thread 653 "cin" received signal SIGABRT, Aborted. > [Switching to Thread 0x7ffb6bfff6c0 (LWP 715674)] > __pthread_kill_implementation (threadid=, > signo=signo@entry=6, > no_tid=no_tid@entry=0) at pthread_kill.c:44 > Downloading source file /usr/src/debug/glibc/glibc/nptl/pthread_kill.c > 44return INTERNAL_SYSCALL_ERROR_P (ret) ? > INTERNAL_SYSCALL_ERRNO (ret) : 0; > (gdb) bt > #0 __pthread_kill_implementation (threadid=, > signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 > #1 0x75fa7953 in __pthread_kill_internal (signo=6, > threadid=) at pthread_kill.c:78 > #2 0x75f58ea8 in __GI_raise (sig=sig@entry=6) > at ../sysdeps/posix/raise.c:26 > #3 0x75f4253d in __GI_abort () at abort.c:79 > #4 0x75f4329e in __libc_message ( > fmt=fmt@entry=0x760ba535 "*** %s ***: terminated\n") > at ../sysdeps/posix/libc_fatal.c:150 > #5 0x76037c5b in __GI___fortify_fail ( > msg=msg@entry=0x760ba51d "stack smashing detected") > at fortify_fail.c:24 > #6 0x76037c36 in __stack_chk_fail () at stack_chk_fail.c:24 > #7 0x560a42bd in BC_WindowEvents::run (this=) > at bcwindowevents.C:138 > #8 0x560aca95 in Thread::entrypoint (parameters=0x7fff38554740) > at thread.C:70 > #9 0x75fa5bb5 in start_thread (arg=) > at pthread_create.c:444 > #10 0x76027d90 in clone3 () > at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 > (gdb) > > -- > Stefan > -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] *** stack smashing detected ***: terminated
[Thread 0x7ffb70db66c0 (LWP 715673) exited] *** stack smashing detected ***: terminated Thread 653 "cin" received signal SIGABRT, Aborted. [Switching to Thread 0x7ffb6bfff6c0 (LWP 715674)] __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 Downloading source file /usr/src/debug/glibc/glibc/nptl/pthread_kill.c 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x75fa7953 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x75f58ea8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x75f4253d in __GI_abort () at abort.c:79 #4 0x75f4329e in __libc_message ( fmt=fmt@entry=0x760ba535 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150 #5 0x76037c5b in __GI___fortify_fail ( msg=msg@entry=0x760ba51d "stack smashing detected") at fortify_fail.c:24 #6 0x76037c36 in __stack_chk_fail () at stack_chk_fail.c:24 #7 0x560a42bd in BC_WindowEvents::run (this=) at bcwindowevents.C:138 #8 0x560aca95 in Thread::entrypoint (parameters=0x7fff38554740) at thread.C:70 #9 0x75fa5bb5 in start_thread (arg=) at pthread_create.c:444 #10 0x76027d90 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 (gdb) -- Stefan -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] *** stack smashing detected ***: terminated
вс, 30 апр. 2023 г., 23:37 Stefan de Konink : > On Sunday, April 30, 2023 10:28:23 PM CEST, Andrew Randrianasulu wrote: > > Well, is this happening with all files from some device? > > No, this happens (reproducibly) for some projects within my currently > dailies. > > > if yes, you can try to pre-process it with ffmpeg and see if > > crash gone try to make smallest possible file still > > crashing, or notice if only certain (bigger?) dimension crash > > ... any additional tracks, unusual codecs, abrupt recording > > abort for this file? > > The problem is: I don't know what actually triggers this, is it the > viewer, > is it something in the timeline. > Well, may be send one of those files to Phyllis so she will try to crash cingg too with it (I think there was upload area for such things). May be try to get debug build of cingg running and then try to get backtrace so we will see where it crashes (even non-debug build probably will give some stacktrace: try 'gdb cin' then 'run' from gdb prompt, and then post result of 'bt full' after it smashes itself > > > > Also, does this happen only with internal ffmpeg or with > > distro-provided shared libav* libs too? Was hardware decoding > > accel involved? > > This is git cingg compiled code, with ArchLinux. Which I tried to get Cuda > working. But as we speak "use hardware dev" is currently set to none. > > -- > Stefan > -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] *** stack smashing detected ***: terminated
On Sunday, April 30, 2023 10:28:23 PM CEST, Andrew Randrianasulu wrote: Well, is this happening with all files from some device? No, this happens (reproducibly) for some projects within my currently dailies. if yes, you can try to pre-process it with ffmpeg and see if crash gone try to make smallest possible file still crashing, or notice if only certain (bigger?) dimension crash ... any additional tracks, unusual codecs, abrupt recording abort for this file? The problem is: I don't know what actually triggers this, is it the viewer, is it something in the timeline. Also, does this happen only with internal ffmpeg or with distro-provided shared libav* libs too? Was hardware decoding accel involved? This is git cingg compiled code, with ArchLinux. Which I tried to get Cuda working. But as we speak "use hardware dev" is currently set to none. -- Stefan -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] *** stack smashing detected ***: terminated
вс, 30 апр. 2023 г., 23:21 Stefan de Konink via Cin < cin@lists.cinelerra-gg.org>: > Any clues how I can make a reproducable case for the following? > Well, is this happening with all files from some device? if yes, you can try to pre-process it with ffmpeg and see if crash gone try to make smallest possible file still crashing, or notice if only certain (bigger?) dimension crash ... any additional tracks, unusual codecs, abrupt recording abort for this file? Also, does this happen only with internal ffmpeg or with distro-provided shared libav* libs too? Was hardware decoding accel involved? > > > file:/home/skinkie/20230430-loerenbijdeboeren/ronin/melkveehouderij-sijben/_DSC2736.MOV > err: Invalid data found when processing input > FFStream::decode: failed > FFStream::decode: avcodec_send_packet failed. > > file:/home/skinkie/20230430-loerenbijdeboeren/ronin/melkveehouderij-sijben/_DSC2736.MOV > err: Invalid data found when processing input > FFStream::decode: failed > *** stack smashing detected ***: terminated > Aborted (core dumped) > > -- > Stefan > -- > Cin mailing list > Cin@lists.cinelerra-gg.org > https://lists.cinelerra-gg.org/mailman/listinfo/cin > -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
