> > >>> Did you test with valgrind? > > > > Attached, is the output of valgrind. Does it make sense? > > No you have to use a binary with debug symbols. > > It may not be necessary to send the output here, I just wanted > to explain that for the kind of error you showed (double free), > a debugger usually cannot help, valgrind (often) does. > > Carl Eugen >
Sometimes is better to use gcc fsanitize family. -fsanitize=address Enable AddressSanitizer, a fast memory error detector. Memory access instructions are instrumented to detect out-of-bounds and use-after-free bugs. The option enables -fsanitize-address-use-after-scope. See https://github.com/google/sanitizers/wiki/AddressSanitizer for more details. The run-time behavior can be influenced using the ASAN_OPTIONS environment variable. When set to help=1, the available options are shown at startup of the instrumented program. See https://github.com/google/sanitizers/wiki/AddressSanitizerFlags#run-time-flags for a list of supported options. The option cannot be combined with -fsanitize=thread and/or -fcheck-pointer-bounds. my 2c Mirko
_______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
