# HG changeset patch # User diego # Date 1030483170 0 # Node ID ed54a7bba26832a8f6f93f2c7c27103ca824bda2 # Parent 9e641d749832e5c1de1b677d5843c27d0036f17f Cosmetics: Some more indents and newlines. diff -r 9e641d749832 -r ed54a7bba268 DOCS/bugreports.html --- a/DOCS/bugreports.html Tue Aug 27 21:00:39 2002 +0000 +++ b/DOCS/bugreports.html Tue Aug 27 21:19:30 2002 +0000 @@ -12,6 +12,7 @@
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 @@ -21,6 +22,7 @@ mplayer-dev-eng 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 @@ -52,6 +54,7 @@ voluntarily in our free time. We are very busy and cannot guarantee that you will get a solution for your problem or even an answer.
+Where to report bugs?
Subscribe to the mplayer-users mailing list:
@@ -65,6 +68,7 @@
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.
What to report?
System Information
@@ -102,6 +106,7 @@ +Hardware & drivers
lspci -vv
output on Linux systems.For compilation problems/errors
Please include these files:
@@ -141,26 +147,27 @@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:
+ 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
If your problem is specific to one or more files, then please upload the -offender(s) to:
+ offender(s) to:ftp://mplayerhq.hu/MPlayer/incoming/
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:
+ 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:
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.
+How to extract meaningful information from a core dump
Please create following command file:
@@ -197,6 +206,7 @@ gdb mplayer --core=core -batch --command=command_file > mplayer.bug
How to conserve information about a reproducible crash
Recompile MPlayer with debugging code enabled:
@@ -219,12 +229,14 @@ and send the complete output to us. +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