How to report bugs?
-First of all please try the latest CVS version of mplayer as your bug might -already be fixed there. CVS instructions can be found at the bottom of +
First of all please try the latest CVS version of MPlayer as your bug +might already be fixed there. CVS instructions can be found at the bottom of this page.
If this did not help please refer to Appendix D @@ -24,7 +24,7 @@
If you feel have the necessary skills you are invited to have a go at fixing the bug yourself. Or maybe you already did that? Please read this short document to find out how to get your -code included in mplayer. The people on the +code included in MPlayer. The people on the mplayer-dev-eng mailing list can assist you if you have questions.
@@ -33,16 +33,19 @@Subscribe to the mplayer-users mailing list:
http://mplayerhq.hu/mailman/listinfo/mplayer-users
and send your bug report to:
- mplayer-users@mplayerhq.hu
-Please note that we will not individually CC (carbon-copy) people so it is a good
-idea to subscribe to actually receive your answer.
The language of this list is English. Please follow the standard +Netiquette Guidelines and +do not send HTML mail to to any of our mailing lists. You will only get +ignored or banned. Also note that we will not individually CC (carbon-copy) +people so it is a good idea to subscribe to actually receive your answer.
Please do not send bug reports privately to individual developers. This is
community work and thus there might be several people interested in it.
Also sometimes other users already experienced your troubles and have a
-solution in hand how to circumvent a problem even if it is a bug in mplayer
-code.
-The language of this list is English.
Please describe your problem as detailed as possible with examples etc. and do not forget to include this valuable information:
@@ -125,10 +128,10 @@For playback problems
-Please include the output of mplayer at verbosity level 1, but remember to -not truncate the output when you paste it into your mail. The developers need -all of the messages to properly diagnose a problem. You can direct the output -into a file like this:
+Please include the output of MPlayer at verbosity level 1, but +remember to not truncate the output when you paste it into your mail. The +developers need all of the messages to properly diagnose a problem. You can +direct the output into a file like this:
mplayer -v [options] [filename] &> mplayer.log
Also upload a small text file having the same base name as your file
with a .txt extension. Describe the problem you are having with the
particular file there and include your email address as well as the output
-of mplayer at verbosity level 1.
+of MPlayer at verbosity level 1.
Usually the first 1-5 MB of a file are enough to reproduce the problem,
but to be sure we ask you to:
dd if=yourfile of=smallfile bs=1024k count=5
For crashes
-If you have a core dump of the crash continue reading the next paragraph, otherwise skip it.
+If you have a core dump of the crash continue reading the next paragraph, +otherwise skip it.
How to extract meaningful information from a core dump
@@ -177,10 +181,10 @@ gdb mplayer --core=core -batch --command=command_file > mplayer.bug
How to conserve information about a reproducible crash
-Re-compile mplayer with debugging code enabled:
+Recompile MPlayer with debugging code enabled:
./configure --enable-debug=3
make
gdb mplayer
You are now within gdb. Type:
@@ -200,7 +204,7 @@I know what I am doing...
If you created a proper bug report following the steps above and you are
-confident it is a bug in mplayer, not a compiler problem or broken file,
+confident it is a bug in MPlayer, not a compiler problem or broken file,
you have already read the documentation and you could not find a solution,
your sound drivers are OK, then you might want to subscribe to the
mplayer-advusers list and send your bug report there to get a better and
@@ -209,7 +213,7 @@
in the manual there, you will be ignored or flamed instead of getting an
appropriate answer.
So do not flame us and subscribe to -advusers only if you really know
-what you are doing and feel like being an advanced mplayer user or
+what you are doing and feel like being an advanced MPlayer user or
developer. If you meet these criteria it should not be difficult to find
out how to subscribe...