comparison DOCS/bugreports.html @ 7814:988498df1996

<B>MPlayer</B> ---> MPlayer

7813:76940a39405a

<P>Good bug reports are a very valuable contribution to the development of any
  software project. But just like writing good software, good problem reports
  involve some work. Please realize that most developers are extremely busy and
  receive obscene amounts of email. So while your feedback is crucial in
  improving <B>MPlayer</B> and very much appreciated, please understand that you
  have to provide <B>all</B> of the information we request and follow the
  instructions in this document closely.</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
  <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>


<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. Development moves extremely fast, most problems
  in official releases are reported within days or even hours, so please use
  <B>only CVS</B> to report bugs. 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

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

</UL>


<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.
  The developers need all of the messages to properly diagnose a problem. You
  can direct the output into a file like this:</P>

<P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;mplayer -v [options] [filename] &amp;&gt; mplayer.log</CODE></P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P>

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

<P>&nbsp;&nbsp;&nbsp;&nbsp;<CODE>gdb mplayer --core=core -batch --command=command_file &gt; mplayer.bug</CODE></P>


<H4>How to conserve information about a reproducible crash</H4>

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>

You are now within gdb. Type:

<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
  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
  in the manual there, you will be ignored or flamed instead of getting an
  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>

</BODY>
</HTML>

7814:988498df1996

<P>Good bug reports are a very valuable contribution to the development of any
  software project. But just like writing good software, good problem reports
  involve some work. Please realize that most developers are extremely busy and
  receive obscene amounts of email. So while your feedback is crucial in
  improving MPlayer and very much appreciated, please understand that you
  have to provide <B>all</B> of the information we request and follow the
  instructions in this document closely.</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
  <A HREF="tech/patches.txt">this short document</A> to find out how to get
  your code included in MPlayer. 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>


<H2>How to report bugs</H2>

<P>First of all please try the latest CVS version of MPlayer as your bug
  might already be fixed there. Development moves extremely fast, most problems
  in official releases are reported within days or even hours, so please use
  <B>only CVS</B> to report bugs. 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

  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.
  Sometimes other users already experienced your troubles and know how to
  circumvent a problem even if it is a bug in MPlayer 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

</UL>


<H4>For playback problems</H4>

<P>Please include the output of MPlayer at verbosity level 1, but
  remember to <B>not truncate the output</B> 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:</P>

<P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;mplayer -v [options] [filename] &amp;&gt; mplayer.log</CODE></P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P>

<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 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:</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>&nbsp;&nbsp;&nbsp;&nbsp;<CODE>gdb mplayer --core=core -batch --command=command_file &gt; mplayer.bug</CODE></P>


<H4>How to conserve information about a reproducible crash</H4>

Recompile MPlayer 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 MPlayer within gdb using:

<P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;gdb ./mplayer</CODE></P>

You are now within gdb. Type:

<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 MPlayer, 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
  in the manual there, you will be ignored or flamed instead of getting an
  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 MPlayer user or
  developer.  If you meet these criteria it should not be difficult to find
  out how to subscribe...</P>

</BODY>
</HTML>