Cosmetics: Indented code and inserted empty lines.

git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@7101 b3059339-0415-0410-9bf9-f77b7e298cf2
This commit is contained in:
diego 2002-08-27 21:00:39 +00:00
parent f833f5b1a5
commit a4724edd07
1 changed files with 120 additions and 112 deletions

View File

@ -15,120 +15,120 @@
<P><B>How to fix bugs</B></P> <P><B>How to fix bugs</B></P>
<P>If you feel have the necessary skills you are invited to have a go at fixing <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 the bug yourself. Or maybe you already did that? Please read
<A HREF="tech/patches.txt">this short document</A> to find out how to get your <A HREF="tech/patches.txt">this short document</A> to find out how to get
code included in <B>MPlayer</B>. The people on the your code included in <B>MPlayer</B>. The people on the
<A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</A> <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</A>
mailing list will assist you if you have questions.</P> mailing list will assist you if you have questions.</P>
<P><B>How to report bugs</B></P> <P><B>How to report bugs</B></P>
<P>First of all please try the latest CVS version of <B>MPlayer</B> as your bug <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 might already be fixed there. CVS instructions can be found at the bottom of
<A HREF="http://www.mplayerhq.hu/homepage/dload.html">this page</A> or in the <A HREF="http://www.mplayerhq.hu/homepage/dload.html">this page</A> or in the
README. If this did not help please refer to README. If this did not help please refer to
<A HREF="documentation.html#known_bugs">the list of known bugs</A> and the rest of the <A HREF="documentation.html#known_bugs">the list of known bugs</A> and the
documentation. If your problem is not known or not solvable by our instructions, rest of the documentation. If your problem is not known or not solvable by our
then please report the bug.</P> instructions, then please report the bug.</P>
<P>Please do not send bug reports privately to individual developers. This is <P>Please do not send bug reports privately to individual developers. This is
community work and thus there might be several people interested in it. community work and thus there might be several people interested in it.
Sometimes other users already experienced your troubles and know how to Sometimes other users already experienced your troubles and know how to
circumvent a problem even if it is a bug in <B>MPlayer</B> code.</P> circumvent a problem even if it is a bug in <B>MPlayer</B> code.</P>
<P>Please describe your problem in as much detail as possible. Do a little <P>Please describe your problem in as much detail as possible. Do a little
detective work to narrow down the circumstances under which the problem occurs. detective work to narrow down the circumstances under which the problem
Does the bug only show up in certain situations? Is it specific to certain files occurs. Does the bug only show up in certain situations? Is it specific to
or file types? Does it occur with only one codec or is it codec independent? certain files or file types? Does it occur with only one codec or is it codec
Can you reproduce it with all output drivers? The more information you provide independent? Can you reproduce it with all output drivers? The more
the better are our chances at fixing your problem. Please do not forget to information you provide the better are our chances at fixing your problem.
also include the valuable information requested below, we will be unable to Please do not forget to also include the valuable information requested below,
properly diagnose your problem otherwise.</P> we will be unable to properly diagnose your problem otherwise.</P>
<P>An excellent and well written guide to asking questions in public forums is <P>An excellent and well written guide to asking questions in public forums is
<A HREF="http://www.tuxedo.org/~esr/faqs/smart-questions.html">How To Ask <A HREF="http://www.tuxedo.org/~esr/faqs/smart-questions.html">How To Ask
Questions The Smart Way</A> by Eric S. Raymond. If you follow these guidelines Questions The Smart Way</A> by Eric S. Raymond. If you follow these guidelines
you should be safe. But please understand that we all follow the mailing lists you should be safe. But please understand that we all follow the mailing lists
voluntarily in our free time. We are very busy and cannot guarantee that you 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. </P> will get a solution for your problem or even an answer.</P>
<P><B>Where to report bugs?</B></P> <P><B>Where to report bugs?</B></P>
<P>Subscribe to the mplayer-users mailing list:<BR> <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> &nbsp;&nbsp;&nbsp;&nbsp;<A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR>
and send your bug report to:<BR> and send your bug report to:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="mailto:mplayer-users@mplayerhq.hu">mplayer-users@mplayerhq.hu</A></P> &nbsp;&nbsp;&nbsp;&nbsp;<A HREF="mailto:mplayer-users@mplayerhq.hu">mplayer-users@mplayerhq.hu</A></P>
<P>The language of this list is <B>English</B>. Please follow the standard <P>The language of this list is <B>English</B>. Please follow the standard
<A HREF="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</A> and <A HREF="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</A> and
<B>do not send HTML mail</B> to any of our mailing lists. You will only get <B>do not send HTML mail</B> to any of our mailing lists. You will only get
ignored or banned. Also note that we will not individually CC (carbon-copy) 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.</P> people so it is a good idea to subscribe to actually receive your answer.</P>
<P><B>What to report?</B></P> <P><B>What to report?</B></P>
<P><B>System Information</B></P> <P><B>System Information</B></P>
<UL> <UL>
<LI>Your Linux distribution or operating system e.g.: <LI>Your Linux distribution or operating system e.g.:
<UL> <UL>
<LI>Red Hat 7.1</LI> <LI>Red Hat 7.1</LI>
<LI>Slackware 7.0 + devel packs from 7.1 ...</LI> <LI>Slackware 7.0 + devel packs from 7.1 ...</LI>
</UL> </UL>
</LI> </LI>
<LI>kernel version:<BR> <LI>kernel version:<BR>
<CODE>uname -a</CODE></LI> <CODE>uname -a</CODE></LI>
<LI>libc version:<BR> <LI>libc version:<BR>
<CODE>ls -l /lib/libc[.-]*</CODE></LI> <CODE>ls -l /lib/libc[.-]*</CODE></LI>
<LI>X version:<BR> <LI>X version:<BR>
<CODE>X -version</CODE></LI> <CODE>X -version</CODE></LI>
<LI>gcc and ld versions:<BR> <LI>gcc and ld versions:<BR>
<CODE>gcc -v<BR> <CODE>gcc -v<BR>
ld -v</CODE></LI> ld -v</CODE></LI>
<LI>binutils version:<BR> <LI>binutils version:<BR>
<CODE>as --version</CODE></LI> <CODE>as --version</CODE></LI>
<LI>If you have problems with fullscreen mode: <LI>If you have problems with fullscreen mode:
<UL> <UL>
<LI>Window manager type and version</LI> <LI>Window manager type and version</LI>
</UL> </UL>
</LI> </LI>
<LI>If only the GUI is buggy: <LI>If only the GUI is buggy:
<UL> <UL>
<LI>GTK version</LI> <LI>GTK version</LI>
<LI>GLIB version</LI> <LI>GLIB version</LI>
<LI>libpng version</LI> <LI>libpng version</LI>
<LI>GUI situation in which the bug occurs</LI> <LI>GUI situation in which the bug occurs</LI>
</UL> </UL>
</LI> </LI>
</UL> </UL>
<P><B>Hardware &amp; drivers</B></P> <P><B>Hardware &amp; drivers</B></P>
<UL> <UL>
<LI>CPU info (this works on Linux only):<BR> <LI>CPU info (this works on Linux only):<BR>
<CODE>cat /proc/cpuinfo</CODE></LI> <CODE>cat /proc/cpuinfo</CODE></LI>
<LI>Video card manufacturer and model, e.g.: <LI>Video card manufacturer and model, e.g.:
<UL> <UL>
<LI>ASUS V3800U chip: nVidia TNT2 Ultra pro 32MB SDRAM</LI> <LI>ASUS V3800U chip: nVidia TNT2 Ultra pro 32MB SDRAM</LI>
<LI>Matrox G400 DH 32MB SGRAM</LI> <LI>Matrox G400 DH 32MB SGRAM</LI>
</UL> </UL>
</LI> </LI>
<LI>Video driver type &amp; version, e.g.: <LI>Video driver type &amp; version, e.g.:
<UL> <UL>
<LI>X built-in driver</LI> <LI>X built-in driver</LI>
<LI>nVidia 0.9.623</LI> <LI>nVidia 0.9.623</LI>
<LI>Utah-GLX CVS 2001-02-17</LI> <LI>Utah-GLX CVS 2001-02-17</LI>
<LI>DRI from X 4.0.3</LI> <LI>DRI from X 4.0.3</LI>
</UL> </UL>
</LI> </LI>
<LI>Sound card type &amp; driver, e.g.: <LI>Sound card type &amp; driver, e.g.:
<UL> <UL>
<LI>Creative SBLive! Gold with OSS driver from oss.creative.com</LI> <LI>Creative SBLive! Gold with OSS driver from oss.creative.com</LI>
<LI>Creative SB16 with kernel OSS drivers</LI> <LI>Creative SB16 with kernel OSS drivers</LI>
<LI>GUS PnP with ALSA OSS emulation</LI> <LI>GUS PnP with ALSA OSS emulation</LI>
</UL> </UL>
</LI> </LI>
<LI>If in doubt include <CODE>lspci -vv</CODE> output on Linux systems.</LI> <LI>If in doubt include <CODE>lspci -vv</CODE> output on Linux systems.</LI>
</UL> </UL>
<P><B>For compilation problems/errors</B></P> <P><B>For compilation problems/errors</B></P>
@ -161,77 +161,85 @@ particular file there and include your email address as well as the output
of <B>MPlayer</B> at verbosity level 1.<BR> of <B>MPlayer</B> at verbosity level 1.<BR>
Usually the first 1-5 MB of a file are enough to reproduce the problem, Usually the first 1-5 MB of a file are enough to reproduce the problem,
but to be sure we ask you to: but to be sure we ask you to:
<P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;dd if=yourfile of=smallfile bs=1024k count=5</CODE></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 <P>It will take the first five megabytes of <STRONG>'your-file'</STRONG> and
write it to <STRONG>'small-file'</STRONG>.<BR> write it to <STRONG>'small-file'</STRONG>.<BR>
Then try again on this small file and if the bug still shows up Then try again on this small file and if the bug still shows up
your sample is sufficient for us.<BR> your sample is sufficient for us.<BR>
Please <STRONG>do not ever</STRONG> send such files via mail! Upload it, 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> 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 If the file is accessible on the net, then sending the
<STRONG>exact</STRONG> URL is sufficient.</P> <STRONG>exact</STRONG> URL is sufficient.</P>
<P><B>For crashes</B></P> <P><B>For crashes</B></P>
<P>If you have a core dump of the crash continue reading the next paragraph, <P>If you have a core dump of the crash continue reading the next paragraph,
otherwise skip it.</P> otherwise skip it.</P>
<P><B>How to extract meaningful information from a core dump</B></P> <P><B>How to extract meaningful information from a core dump</B></P>
<P>Please create following command file:</P> <P>Please create following command file:</P>
<P><CODE>disass $eip-32 $eip+32<BR> <P><CODE>disass $eip-32 $eip+32<BR>
printf "eax=%08lX\n",$eax<BR> printf "eax=%08lX\n",$eax<BR>
printf "ebx=%08lX\n",$ebx<BR> printf "ebx=%08lX\n",$ebx<BR>
printf "ecx=%08lX\n",$ecx<BR> printf "ecx=%08lX\n",$ecx<BR>
printf "edx=%08lX\n",$edx<BR> printf "edx=%08lX\n",$edx<BR>
printf "esp=%08lX\n",$esp<BR> printf "esp=%08lX\n",$esp<BR>
printf "ebp=%08lX\n",$ebp<BR> printf "ebp=%08lX\n",$ebp<BR>
printf "edi=%08lX\n",$edi<BR> printf "edi=%08lX\n",$edi<BR>
printf "esi=%08lX\n",$esi<BR> printf "esi=%08lX\n",$esi<BR>
</CODE></P> </CODE></P>
<P>Then simply execute the following on your command line:</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>&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> <P><B>How to conserve information about a reproducible crash</B></P>
<P>Recompile <B>MPlayer</B> with debugging code enabled:</P> <P>Recompile <B>MPlayer</B> with debugging code enabled:</P>
<P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;./configure --enable-debug=3<BR> <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;./configure --enable-debug=3<BR>
&nbsp;&nbsp;&nbsp;&nbsp;make</CODE></P> &nbsp;&nbsp;&nbsp;&nbsp;make</CODE></P>
and then run <B>MPlayer</B> within gdb using: and then run <B>MPlayer</B> within gdb using:
<P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;gdb mplayer</CODE></P> <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;gdb mplayer</CODE></P>
<P>You are now within gdb. Type:</P> <P>You are now within gdb. Type:</P>
<P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;run -v [options-to-mplayer] filename</code></P> <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;run -v [options-to-mplayer] filename</code></P>
and reproduce your crash. As soon as you did it, gdb will and reproduce your crash. As soon as you did it, gdb will
return you to the command line prompt where you have to enter return you to the command line prompt where you have to enter
<P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;bt<BR> <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;bt<BR>
&nbsp;&nbsp;&nbsp;&nbsp;disass $eip-32 $eip+32</CODE></P> &nbsp;&nbsp;&nbsp;&nbsp;disass $eip-32 $eip+32</CODE></P>
and send the complete output to us. and send the complete output to us.
<P><B>General note</B></P> <P><B>General note</B></P>
<P>If something is quite big (logs for instance) then it is better to upload <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 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> include only the path and filename in your bug report.</P>
<P><B>I know what I am doing...</B></P> <P><B>I know what I am doing...</B></P>
<P>If you created a proper bug report following the steps above and you are <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 file, confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken
you have already read the documentation and you could not find a solution, file, you have already read the documentation and you could not find a
your sound drivers are OK, then you might want to subscribe to the 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 mplayer-advusers list and send your bug report there to get a better and
faster answer.<BR><BR> faster answer.<BR><BR>
Please be advised that if you post newbie questions or questions answered Please be advised that if you post newbie questions or questions answered
in the manual there, you will be ignored or flamed instead of getting an in the manual there, you will be ignored or flamed instead of getting an
appropriate answer.<BR> appropriate answer.<BR>
So do not flame us and subscribe to -advusers only if you really know So do not flame us and subscribe to -advusers only if you really know
what you are doing and feel like being an advanced <B>MPlayer</B> user or what you are doing and feel like being an advanced <B>MPlayer</B> user or
developer. If you meet these criteria it should not be difficult to find developer. If you meet these criteria it should not be difficult to find
out how to subscribe... out how to subscribe...</P>
</P>
</BODY> </BODY>
</HTML> </HTML>