RepoMirrors
/
mpv
mirror of https://github.com/mpv-player/mpv
1
0
Fork 0
Code Issues Releases Wiki Activity

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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
DOCS/bugreports.html
View File

@ -16,8 +16,8 @@
<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
<A HREF="tech/patches.txt">this short document</A> to find out how to get your
code included in <B>MPlayer</B>. The people on the
<A HREF="tech/patches.txt">this short document</A> to find out how to get
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>
mailing list will assist you if you have questions.</P>
@ -27,9 +27,9 @@ mailing list will assist you if you have questions.</P>
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
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
documentation. If your problem is not known or not solvable by our instructions,
then please report the bug.</P>
<A HREF="documentation.html#known_bugs">the list of known bugs</A> and the
rest of the documentation. If your problem is not known or not solvable by our
instructions, then please report the bug.</P>
<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.
@ -37,13 +37,13 @@ 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>
<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.
Does the bug only show up in certain situations? Is it specific to certain files
or file types? Does it occur with only one codec or is it codec independent?
Can you reproduce it with all output drivers? The more information you provide
the better are our chances at fixing your problem. Please do not forget to
also include the valuable information requested below, we will be unable to
properly diagnose your problem otherwise.</P>
detective work to narrow down the circumstances under which the problem
occurs. Does the bug only show up in certain situations? Is it specific to
certain files or file types? Does it occur with only one codec or is it codec
independent? Can you reproduce it with all output drivers? The more
information you provide the better are our chances at fixing your problem.
Please do not forget to also include the valuable information requested below,
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
<A HREF="http://www.tuxedo.org/~esr/faqs/smart-questions.html">How To Ask
@ -161,6 +161,7 @@ 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:
<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
@ -193,21 +194,29 @@ printf "esi=%08lX\n",$esi<BR>
</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>
<P>Recompile <B>MPlayer</B> with debugging code enabled:</P>
<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>
<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
return you to the command line prompt where you have to enter
<P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;bt<BR>
&nbsp;&nbsp;&nbsp;&nbsp;disass $eip-32 $eip+32</CODE></P>
and send the complete output to us.
<P><B>General note</B></P>
@ -219,9 +228,9 @@ include only the path and filename in your bug report.</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
confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken file,
you have already read the documentation and you could not find a solution,
your sound drivers are OK, then you might want to subscribe to the
confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken
file, you have already read the documentation and you could not find a
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
faster answer.<BR><BR>
Please be advised that if you post newbie questions or questions answered
@ -230,8 +239,7 @@ appropriate answer.<BR>
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
developer. If you meet these criteria it should not be difficult to find
out how to subscribe...
</P>
out how to subscribe...</P>
</BODY>
</HTML>