[FFmpeg-devel] [PATCH 1/2] bugreports: suggest to include valgrind output.

Nicolas George nicolas.george at normalesup.org
Sat Jun 23 10:39:41 CEST 2012

Signed-off-by: Nicolas George <nicolas.george at normalesup.org>
 src/bugreports |   17 +++++++++++++++--
 1 file changed, 15 insertions(+), 2 deletions(-)

diff --git a/src/bugreports b/src/bugreports
index 04706f8..6736d2f 100644
--- a/src/bugreports
+++ b/src/bugreports
@@ -50,8 +50,12 @@ tracking regressions in old revisions.
 If you encounter a crash bug, please provide the <code>gdb</code> output,
-backtrace and disassembly using the the <code>ffmpeg_g</code> debug binary as
+backtrace and disassembly, and if possible the <code>valgrind<code> output,
+using the the <code>ffmpeg_g</code> debug binary.
+For <code>gdb</code>, proceed as follows:
@@ -83,6 +87,15 @@ info all-registers
 With older <code>gdb</code> versions, use <code>disass $pc-32 $pc+32</code>.
+For <code>valgrind</code>, run the following command and copy/paste the
+output into your bug report:
+<pre>valgrind ffmpeg_g <rest of command line></pre>
 <h2>Bug Tracker</h2>

More information about the ffmpeg-devel mailing list