[FFmpeg-devel] [PATCH 2/2] configure: disable stripping and memory_poisoning in various toolchains

wm4 nfxjfg at googlemail.com
Mon Apr 10 09:53:09 EEST 2017


On Mon, 10 Apr 2017 07:54:41 +0200
Clément Bœsch <u at pkh.me> wrote:

> On Mon, Apr 10, 2017 at 03:51:40AM +0200, Michael Niedermayer wrote:
> > On Sun, Apr 09, 2017 at 06:46:51PM +0200, Clément Bœsch wrote:  
> > > Toolchains which target debugging are meaningless with stripping and
> > > toolchains which target memory tracking are meaningless with memory
> > > pollution.
> > > ---
> > >  configure | 8 ++++++++
> > >  1 file changed, 8 insertions(+)  
> > 
> > memory_poisoning is not enabled by default in configure
> >   
> 
> but it is enabled by the fate configure, so if you create a FATE instance
> with valgrind, you may forget that memory-poisoning is enabled and make it
> useless for uninitialized memory without realizing.

I love it when such questionable debugging features interfere with real
debugging tools.


More information about the ffmpeg-devel mailing list