Appendix C - How to report bugs
+How to fix bugs
+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 @@ -23,7 +23,7 @@ mailing list will assist you if you have questions.
-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 @@ -55,7 +55,7 @@ will get a solution for your problem or even an answer.
-Where to report bugs?
+Subscribe to the mplayer-users mailing list:
http://mplayerhq.hu/mailman/listinfo/mplayer-users
@@ -69,9 +69,9 @@
people so it is a good idea to subscribe to actually receive your answer.
What to report?
+System Information
+Hardware & drivers
+For compilation problems/errors
+Please include these files:
+Please include these files: +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. @@ -165,29 +166,27 @@
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.
- Usually the first 1-5 MB of a file are enough to reproduce the problem,
- but to be sure we ask you to:
+ 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
It will take the first five megabytes of 'your-file' and
- write it to 'small-file'.
- Then try again on this small file and if the bug still shows up
- your sample is sufficient for us.
- Please do not ever send such files via mail! Upload it,
- and send only the path/filename of the file on the FTP-server.
- If the file is accessible on the net, then sending the
- exact URL is sufficient.
For crashes
+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
+Please create following command file:
@@ -199,25 +198,25 @@ printf "esp=%08lX\n",$espThen simply execute the following on your command line:
gdb mplayer --core=core -batch --command=command_file > mplayer.bug
How to conserve information about a reproducible crash
+Recompile MPlayer with debugging code enabled:
+Recompile MPlayer with debugging code enabled: ./configure --enable-debug=3
make
gdb mplayer
You are now within gdb. Type:
+You are now within gdb. Type: run -v [options-to-mplayer] filename
General note
+If something is quite big (logs for instance) then it is better to upload it to the FTP server in a compressed format (gzip and bzip preferred) and include only the path and filename in your bug report.
-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