From 5725abb1b2206b55192c5e414629f0974145c34a Mon Sep 17 00:00:00 2001 From: diego Date: Tue, 27 Aug 2002 21:32:35 +0000 Subject: Added proper heading tags and fixed the HTML structure. git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@7103 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/bugreports.html | 57 ++++++++++++++++++++++++++-------------------------- 1 file changed, 28 insertions(+), 29 deletions(-) (limited to 'DOCS/bugreports.html') diff --git a/DOCS/bugreports.html b/DOCS/bugreports.html index a7eb4ca0a2..58cab4cac8 100644 --- a/DOCS/bugreports.html +++ b/DOCS/bugreports.html @@ -10,10 +10,10 @@ -

Appendix C - How to report bugs

How to fix 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

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?

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?

What to report?

System Information

System Information:

Your Linux distribution or operating system e.g.: @@ -107,7 +107,7 @@

Hardware & drivers

Hardware & drivers:

CPU info (this works on Linux only):
@@ -137,9 +137,10 @@

For compilation problems/errors

For compilation problems/errors

+ +Please include these files: -

Please include these files:

configure.log
config.h

For playback problems

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.

+ 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

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

How to extract meaningful information from a core dump

Please create following command file:

@@ -199,25 +198,25 @@ printf "esp=%08lX\n",$esp
printf "ebp=%08lX\n",$ebp
printf "edi=%08lX\n",$edi
- printf "esi=%08lX\n",$esi
-

+ printf "esi=%08lX\n",$esi

Then 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

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

and then run MPlayer within gdb using: +

gdb mplayer

You are now within gdb. Type:

+You are now within gdb. Type:

run -v [options-to-mplayer] filename

@@ -230,14 +229,14 @@ return you to the command line prompt where you have to enter and send the complete output to us. -

General note

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...

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 -- cgit v1.2.3