changeset 7102:a3eefdc6e640

Added proper heading tags and fixed the HTML structure.
author diego
date Tue, 27 Aug 2002 21:32:35 +0000
parents ed54a7bba268
children da10c0756649
files DOCS/bugreports.html
diffstat 1 files changed, 28 insertions(+), 29 deletions(-) [+]
line wrap: on
line diff
--- a/DOCS/bugreports.html	Tue Aug 27 21:19:30 2002 +0000
+++ b/DOCS/bugreports.html	Tue Aug 27 21:32:35 2002 +0000
@@ -10,10 +10,10 @@
 <BODY>
 
 
-<P><B><A NAME=C>Appendix C - How to report bugs</A></B></P>
+<H1><A NAME=C>Appendix C - How to report bugs</A></H1>
 
 
-<P><B>How to fix bugs</B></P>
+<H2>How to fix bugs</H2>
 
 <P>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.</P>
 
 
-<P><B>How to report bugs</B></P>
+<H2>How to report bugs</H2>
 
 <P>First of all please try the latest CVS version of <B>MPlayer</B> 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.</P>
 
 
-<P><B>Where to report bugs?</B></P>
+<H3>Where to report bugs?</H3>
 
 <P>Subscribe to the mplayer-users mailing list:<BR>
   &nbsp;&nbsp;&nbsp;&nbsp;<A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR>
@@ -69,9 +69,9 @@
   people so it is a good idea to subscribe to actually receive your answer.</P>
 
 
-<P><B>What to report?</B></P>
+<H3>What to report?</H3>
 
-<P><B>System Information</B></P>
+<H4>System Information:</H4>
 
 <UL>
   <LI>Your Linux distribution or operating system e.g.:
@@ -107,7 +107,7 @@
 </UL>
 
 
-<P><B>Hardware &amp; drivers</B></P>
+<H4>Hardware &amp; drivers:</H4>
 
 <UL>
   <LI>CPU info (this works on Linux only):<BR>
@@ -137,9 +137,10 @@
 </UL>
 
 
-<P><B>For compilation problems/errors</B></P>
+<H4>For compilation problems/errors</H4>
 
-<P><B>Please include these files:</B></P>
+Please include these files:
+
 <UL>
   <LI>configure.log</LI>
   <LI>config.h</LI>
@@ -148,7 +149,7 @@
 </UL>
 
 
-<P><B>For playback problems</B></P>
+<H4>For playback problems</H4>
 
 <P>Please include the output of <B>MPlayer</B> at verbosity level 1, but
   remember to <B>not truncate the output</B> when you paste it into your mail.
@@ -165,29 +166,27 @@
 <P>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 <B>MPlayer</B> at verbosity level 1.<BR> 
-  Usually the first 1-5 MB of a file are enough to reproduce the problem,
-  but to be sure we ask you to:
+  of <B>MPlayer</B> 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:</P>
 
 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;dd if=yourfile of=smallfile bs=1024k count=5</CODE></P>
 
 <P>It will take the  first five megabytes of <STRONG>'your-file'</STRONG> and
-  write it to <STRONG>'small-file'</STRONG>.<BR>
-  Then try again on this small file and if the bug still shows up 
-  your sample is sufficient for us.<BR>
-  Please <STRONG>do not ever</STRONG> send such files via mail! Upload it,
-  and send only the path/filename of the file on the FTP-server.<BR>
-  If the file is accessible on the net, then sending the
-  <STRONG>exact</STRONG> URL is sufficient.</P>
+  write it to <STRONG>'small-file'</STRONG>. Then try again on this small file
+  and if the bug still shows up your sample is sufficient for us. Please
+  <STRONG>do not ever</STRONG> 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 <STRONG>exact</STRONG> URL is
+  sufficient.</P>
 
 
-<P><B>For crashes</B></P>
+<H4>For crashes</H4>
 
 <P>If you have a core dump of the crash continue reading the next paragraph,
   otherwise skip it.</P>
 
 
-<P><B>How to extract meaningful information from a core dump</B></P>
+<H4>How to extract meaningful information from a core dump</H4>
 
 <P>Please create following command file:</P>
 
@@ -199,25 +198,25 @@
   printf "esp=%08lX\n",$esp<BR>
   printf "ebp=%08lX\n",$ebp<BR>
   printf "edi=%08lX\n",$edi<BR>
-  printf "esi=%08lX\n",$esi<BR>
-  </CODE></P>
+  printf "esi=%08lX\n",$esi</CODE></P>
 
 <P>Then simply execute the following on your command line:</P>
 
 <P>&nbsp;&nbsp;&nbsp;&nbsp;<CODE>gdb mplayer --core=core -batch --command=command_file &gt; mplayer.bug</CODE></P>
 
 
-<P><B>How to conserve information about a reproducible crash</B></P>
+<H4>How to conserve information about a reproducible crash</H4>
 
-<P>Recompile <B>MPlayer</B> with debugging code enabled:</P>
+Recompile <B>MPlayer</B> with debugging code enabled:
 
 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;./configure --enable-debug=3<BR>
   &nbsp;&nbsp;&nbsp;&nbsp;make</CODE></P>
 
 and then run <B>MPlayer</B> within gdb using:
+
 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;gdb mplayer</CODE></P>
 
-<P>You are now within gdb. Type:</P>
+You are now within gdb. Type:
 
 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;run -v [options-to-mplayer] filename</code></P>
 
@@ -230,14 +229,14 @@
 and send the complete output to us.
 
 
-<P><B>General note</B></P>
+<H3>General note</H3>
 
 <P>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.</P>
 
 
-<P><B>I know what I am doing...</B></P>
+<H2>I know what I am doing...</H2>
 
 <P>If you created a proper bug report following the steps above and you are
   confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken