No, etj, I didn't when I wrote it, but now that my debugger memory is engaged I realize I've conflated C and perl. What can I say, when I leak wrongness, it comes out C?
2024-12-20 19:14:46,846 - Starting watermarking process... 2024-12-20 19:26:50,578 - Watermarked video created successfully: /med +ia/fritz/E4B0-3FC2/2024-12-20/Tim_Ballard_20241211_1_watermarked.mp4 Final watermarked video is at: Moviepy - Building video /media/fritz/E +4B0-3FC2/2024-12-20/Tim_Ballard_20241211_1_watermarked.mp4. MoviePy - Writing audio in Tim_Ballard_20241211_1_watermarkedTEMP_MPY_ +wvf_snd.mp4 MoviePy - Done. Moviepy - Writing video /media/fritz/E4B0-3FC2/2024-12-20/Tim_Ballard_ +20241211_1_watermarked.mp4 Moviepy - Done ! Moviepy - video ready /media/fritz/E4B0-3FC2/2024-12-20/Tim_Ballard_20 +241211_1_watermarked.mp4 /media/fritz/E4B0-3FC2/2024-12-20/Tim_Ballard_20241211_1_watermarked.m +p4 Debugged program terminated. Use q to quit or R to restart, use o inhibit_exit to avoid stopping after program termination, h q, h R or h o to get additional info. DB<1>
Finally got it wrangled with perl -d....
In reply to Re^2: Using the writeup and gdb to find mistakes
by Aldebaran
in thread Using the writeup and gdb to find mistakes
by Aldebaran
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |