Valgrind_ I'd even say
log: Print a full backtrace along with error messages under Valgrind On Mon, Mar 23, 2015 at 11:29:23PM +0000, Vittorio Giovara wrote: > Useful to understand where and in what execution state a certain message > is generated. It is enabled only when optimizations are disabled, since > function names are not print otherwise. print_ED > --- a/configure > +++ b/configure > @@ -315,6 +315,8 @@ Developer options (useful when working on Libav itself): > (group) and PROB the probability associated with > NAME (default 0.5). > --random-seed=VALUE seed value for --enable/disable-random > + --disable-valgrind-backtrace do not print a backtrace under Valgrind > + (needs --disable-optimizations) I don't like this. Why not automatically enable it when optimizations are disabled instead? Diego _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
