[FFmpeg-devel] [PATCH 11/13] bugreports: update and cleanup
Clément Bœsch
ubitux at gmail.com
Fri Jan 13 22:08:52 CET 2012
From: Luca Barbato <lu_zero at gentoo.org>
Try to remove historical rant and other childish expressions and add
a reference to valgrind.
---
src/bugreports | 62 ++++++++++++++++++-------------------------------------
1 files changed, 20 insertions(+), 42 deletions(-)
diff --git a/src/bugreports b/src/bugreports
index 04706f8..e876132 100644
--- a/src/bugreports
+++ b/src/bugreports
@@ -1,29 +1,7 @@
<h1>Reporting a Bug To The FFmpeg Project</h1>
<p>
-First of all, please remember that all the developers working on FFmpeg are
-volunteers, we are not paid for analyzing, debugging, fixing and answering
-bug reports. While we try our best to create high quality software and be
-responsive, if you should not get an answer, please consider the above and
-be aware of the fact that we receive many bug reports and the amount of
-time it takes to deal with them can be substantial. Nevertheless most issues
-get resolved, just please understand that there are no guarantees nor
-promises.
-</p>
-
-<p>
-<b>Before reporting a bug, please consider the following items</b>:
-</p>
-
-<p>
-FFmpeg is in a state of perpetual development and we do not currently have the
-person power to backport fixes to official releases. As such, if you wish to
-query or report a bug, you must try with the <b>latest development branch</b> revision of
-FFmpeg to confirm the issue still exists.
-</p>
-
-<p>
-When writing your bug report, please include (uncompressed):
+When writing your bug report, please include:
</p>
<ul>
<li>What you were trying to accomplish (e.g., "I am trying to transcode
@@ -31,7 +9,7 @@ When writing your bug report, please include (uncompressed):
<li>The problem you encountered (e.g., "<code>ffmpeg</code> crashed" or "The
output video was all green")</li>
<li>The exact command line you were using (e.g., "<code>ffmpeg -i input.mov
- -an -vcodec foo output.avi</code>")</li>
+ -an -c:v foo output.avi</code>")</li>
<li>The full, uncut console output provided by
<code>ffmpeg -v 9 -loglevel 99 -i </code> followed by the name of your input file
(copy/pasted from the console, including the banner that indicates
@@ -86,13 +64,23 @@ With older <code>gdb</code> versions, use <code>disass $pc-32 $pc+32</code>.
<h2>Bug Tracker</h2>
<p>
+If gdb does not provide useful information please try to use
+<a href="http://valgrind.org">valgrind</a> to trace possible memory
+corruption.
+</p>
+
+<blockquote>
+<pre>
+valgrind ffmpeg <rest of command line>
+</pre>
+</blockquote>
+
+<p>
Once you have gathered this information, you can submit a report to the
<a href="https://ffmpeg.org/trac/ffmpeg">FFmpeg bug tracker</a>.
Note, you must <a href="https://ffmpeg.org/trac/ffmpeg/register">register</a>
there first before you can submit a report.
You should provide all information so that anyone can reproduce the bug.
-Please do not report your problem on the developer mailing list:
-Only send bug reports there if you also intend to provide a fix.
</p>
@@ -112,28 +100,18 @@ your problem. In this case, please follow these steps:
<li>Please choose descriptive names like "h264_green_tint.mov" or
"block_artifacts_after_seeking.mkv". We already have plenty of "bug.rm"
and "sample.avi" to choose from.</li>
- <li>Upload the sample to the MPlayer FTP server. Note that our FTP server
- is write-only, as it would immediately get misused for warez trading
- otherwise. Do not let this confuse you. Even though you cannot see the
- stuff you upload, it will be there and the FFmpeg developers will have
- access.
+ <li>Upload the sample to the FFmpeg FTP server. Note that our FTP server
+ is write-only in order to prevent abuses. Do not let this confuse you.
+ Even though you cannot see the file you uploaded, it will be there and
+ the FFmpeg developers will have access.
<ul>
<li>Log into upload.ffmpeg.org with an anonymous FTP login.</li>
<li>cd -> incoming</li>
<li>Upload a brief text file describing the sample and what is wrong.
- <b>This is important!</b> If you leave out the text file, your
- sample will most likely be deleted without further examination.</li>
+ <b>This is important!</b> If you leave out the text file it would
+ be harder for us to figure out where to archive it.</li>
<li>Upload the sample.</li>
</ul>
</li>
<li>Email the list and indicate the location of the sample.</li>
</ul>
-
-<p>
-<b>Important: Movie files which have been compressed (rar,7z,gzip,...) will be
-deleted without being examined unless they are raw RGB/YUV/PCM.</b>
-<b>Furthermore movie files uploaded to services like megaupload, rapidshare or
-any other similar service will be ignored. We are not willing to spend our
-time fighting with this ridiculous, bloated and spam-filled crap.</b>
-</p>
-
--
1.7.8.3
More information about the ffmpeg-devel
mailing list