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

[Hendrik Leppkes]

On Mon, Apr 10, 2017 at 8:53 AM, wm4 <nfxjfg at googlemail.com> wrote:
> 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.

Memory poisoning is quite useful, really, and its just a configure
flag like any other, disabled by default.
IMHO, if someone sets up a valgrind box, its his job to remember to
turn this off. configure should not disable explicitly set configure
flags.

- Hendrik