[FFmpeg-cvslog] [ffmpeg-web] branch master updated. fc81887 bugreports: suggest the gdb --args syntax.
gitolite
ffmpeg-cvslog at ffmpeg.org
Sat Jun 23 22:59:37 CEST 2012
The branch, master has been updated
via fc81887c7d65932e79b4b78a48db6b0bcc9bc04f (commit)
via ec09800eb0165b47a0a69bf4c4984c8e57e4d221 (commit)
from 6cbb3e2fee39f9388f6d9f83a35023149ace53f4 (commit)
- Log -----------------------------------------------------------------
commit fc81887c7d65932e79b4b78a48db6b0bcc9bc04f
Author: Nicolas George <nicolas.george at normalesup.org>
AuthorDate: Sat Jun 23 10:37:15 2012 +0200
Commit: Nicolas George <nicolas.george at normalesup.org>
CommitDate: Sat Jun 23 10:37:15 2012 +0200
bugreports: suggest the gdb --args syntax.
It is easier to add gdb --args in front of the command line
from the shell history than to re-type it at the gdb prompt.
diff --git a/src/bugreports b/src/bugreports
index 6736d2f..95b4ed4 100644
--- a/src/bugreports
+++ b/src/bugreports
@@ -72,6 +72,11 @@ In <code>gdb</code>, type 'r' for run, along with the rest of the
</blockquote>
<p>
+(Alternatively, you can run <code>gdb --args ffmpeg_g <rest of command
+line></code> and just type 'r' at the <code>gdb</code> prompt.)
+</p>
+
+<p>
When <code>gdb</code> encounters its problem, run the following commands and
copy/paste the output into your bug report:
</p>
commit ec09800eb0165b47a0a69bf4c4984c8e57e4d221
Author: Nicolas George <nicolas.george at normalesup.org>
AuthorDate: Sat Jun 23 10:33:11 2012 +0200
Commit: Nicolas George <nicolas.george at normalesup.org>
CommitDate: Sat Jun 23 10:33:11 2012 +0200
bugreports: suggest to include valgrind output.
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.
<p>
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
-follows:
+backtrace and disassembly, and if possible the <code>valgrind<code> output,
+using the the <code>ffmpeg_g</code> debug binary.
+</p>
+
+<p>
+For <code>gdb</code>, proceed as follows:
</p>
<blockquote>
@@ -83,6 +87,15 @@ info all-registers
With older <code>gdb</code> versions, use <code>disass $pc-32 $pc+32</code>.
</p>
+<p>
+For <code>valgrind</code>, run the following command and copy/paste the
+output into your bug report:
+</p>
+
+<blockquote>
+<pre>valgrind ffmpeg_g <rest of command line></pre>
+</blockquote>
+
<h2>Bug Tracker</h2>
<p>
-----------------------------------------------------------------------
Summary of changes:
src/bugreports | 22 ++++++++++++++++++++--
1 files changed, 20 insertions(+), 2 deletions(-)
hooks/post-receive
--
More information about the ffmpeg-cvslog
mailing list