On Mon, Jul 02, 2018 at 23:14:51 +0100, Budge wrote:
> I still do not understand, however, why I am getting the segmentation
> fault from AtomicParsley but will try again after running ffmpeg
> using -vn.
Is AtomicParsley not segfaulting for you on each and every file? Even
though it properly reports the atoms?
I had that, and found it to be a quite obvious bug. I crafted my own
patch around 2015, but only in 2018 did someone open a bug ticket:
https://bitbucket.org/wez/atomicparsley/issues/58/segmentation-fault
My fix is attached. Perhaps it's for the same segfault as yours.
(Otherwise: build AtomicParsley with debug symbols and run under gdb.)
Cheers,
Moritz
diff -ur wez-atomicparsley-da2f6e4fc120/src/util.cpp
wez-atomicparsley-da2f6e4fc120-segfault/src/util.cpp
--- wez-atomicparsley-da2f6e4fc120/src/util.cpp 2014-03-03 20:18:56.000000000
+0100
+++ wez-atomicparsley-da2f6e4fc120-segfault/src/util.cpp 2015-05-12
11:26:24.000000000 +0200
@@ -112,8 +112,12 @@
file_opened = true;
}
} else {
+ if ( !open && !file_opened ) {
+ fprintf(stderr, "AtomicParsley internal warning: can't
close %s, already closed\n", utf8file);
+ } else {
fclose(source_file);
file_opened = false;
+ }
}
return source_file;
}
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
