#1505(undetermined:new): Memory poisoning
#1505: Memory poisoning -------------------------------------+------------------------------------- Reporter: ubitux | Owner: Type: | Status: new enhancement | Component: Priority: normal | undetermined Version: | Keywords: unspecified | Blocking: Blocked By: | Analyzed by developer: 0 Reproduced by developer: 0 | -------------------------------------+------------------------------------- It would be nice to have a --enable-memory-poisoning configure switch to make av_malloc() fill the memory with arbitrary random data. This could be enabled by default in tests/fate.sh:configure to do better memory testing on all FATE instances without needing an advanced an slow tool like valgrind. Note: we should fill the requested size *and* padding. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1505> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
#1505: Memory poisoning -------------------------------------+------------------------------------- Reporter: ubitux | Owner: Type: enhancement | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Description changed by ubitux: Old description:
It would be nice to have a --enable-memory-poisoning configure switch to make av_malloc() fill the memory with arbitrary random data. This could be enabled by default in tests/fate.sh:configure to do better memory testing on all FATE instances without needing an advanced an slow tool like valgrind.
Note: we should fill the requested size *and* padding.
New description: It would be nice to have a --enable-memory-poisoning configure switch to make av_malloc()/av_realloc() fill the memory with arbitrary or random data. This could be enabled by default in tests/fate.sh:configure to do better memory testing on all FATE instances without needing an advanced an slow tool like valgrind. -- -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1505#comment:1> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
#1505: Memory poisoning -------------------------------------+------------------------------------- Reporter: ubitux | Owner: ubitux Type: enhancement | Status: open Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by ubitux): * owner: => ubitux * status: new => open -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1505#comment:2> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
#1505: Memory poisoning -------------------------------------+------------------------------------- Reporter: ubitux | Owner: ubitux Type: enhancement | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: fixed Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by ubitux): * status: open => closed * resolution: => fixed Comment: Added in 7c84e7d33762a4bccc0002476a3b20e0b8f26fcc -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1505#comment:3> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
participants (1)
-
FFmpeg