Mercurial > mplayer.hg
comparison DOCS/bugreports.html @ 6470:7051757b01df
HTML mail not wanted, mplayer --> <B>MPlayer</B>.
| author | diego |
|---|---|
| date | Thu, 20 Jun 2002 11:52:51 +0000 |
| parents | 5238266d8b34 |
| children | 210db1a84098 |
comparison
equal
deleted
inserted
replaced
| 6469:caac66533fa0 | 6470:7051757b01df |
|---|---|
| 11 | 11 |
| 12 <P><B><A NAME=C>Appendix C - How to report bugs</A></B></P> | 12 <P><B><A NAME=C>Appendix C - How to report bugs</A></B></P> |
| 13 | 13 |
| 14 <P><B>How to report bugs?</B></P> | 14 <P><B>How to report bugs?</B></P> |
| 15 | 15 |
| 16 <P>First of all please try the latest CVS version of mplayer as your bug might | 16 <P>First of all please try the latest CVS version of <B>MPlayer</B> as your bug |
| 17 already be fixed there. CVS instructions can be found at the bottom of | 17 might already be fixed there. CVS instructions can be found at the bottom of |
| 18 <A HREF="http://www.mplayerhq.hu/homepage/dload.html">this page</A>.</P> | 18 <A HREF="http://www.mplayerhq.hu/homepage/dload.html">this page</A>.</P> |
| 19 | 19 |
| 20 <P>If this did not help please refer to <A HREF="documentation.html#D">Appendix D</A> | 20 <P>If this did not help please refer to <A HREF="documentation.html#D">Appendix D</A> |
| 21 and the rest of the documentation. If your problem is not known or not solvable by | 21 and the rest of the documentation. If your problem is not known or not solvable by |
| 22 our instructions, then please report the bug.</P> | 22 our instructions, then please report the bug.</P> |
| 23 | 23 |
| 24 <P>If you feel have the necessary skills you are invited to have a go at fixing | 24 <P>If you feel have the necessary skills you are invited to have a go at fixing |
| 25 the bug yourself. Or maybe you already did that? Please read | 25 the bug yourself. Or maybe you already did that? Please read |
| 26 <A HREF="tech/patches.txt">this short document</A> to find out how to get your | 26 <A HREF="tech/patches.txt">this short document</A> to find out how to get your |
| 27 code included in mplayer. The people on the | 27 code included in <B>MPlayer</B>. The people on the |
| 28 <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</A> | 28 <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</A> |
| 29 mailing list can assist you if you have questions.</P> | 29 mailing list can assist you if you have questions.</P> |
| 30 | 30 |
| 31 <P><B>Where to report bugs?</B></P> | 31 <P><B>Where to report bugs?</B></P> |
| 32 | 32 |
| 33 <P>Subscribe to the mplayer-users mailing list:<BR> | 33 <P>Subscribe to the mplayer-users mailing list:<BR> |
| 34 <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR> | 34 <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR> |
| 35 and send your bug report to:<BR> | 35 and send your bug report to:<BR> |
| 36 <A HREF="mailto:mplayer-users@mplayerhq.hu">mplayer-users@mplayerhq.hu</A><BR> | 36 <A HREF="mailto:mplayer-users@mplayerhq.hu">mplayer-users@mplayerhq.hu</A></P> |
| 37 Please note that we will not individually CC (carbon-copy) people so it is a good | 37 |
| 38 idea to subscribe to actually receive your answer.</P> | 38 <P>The language of this list is <B>English</B>. Please follow the standard |
| 39 <A HREF="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</A> and | |
| 40 <B>do not send HTML mail</B> to to any of our mailing lists. You will only get | |
| 41 ignored or banned. Also note that we will not individually CC (carbon-copy) | |
| 42 people so it is a good idea to subscribe to actually receive your answer.</P> | |
| 39 | 43 |
| 40 <P>Please do not send bug reports privately to individual developers. This is | 44 <P>Please do not send bug reports privately to individual developers. This is |
| 41 community work and thus there might be several people interested in it. | 45 community work and thus there might be several people interested in it. |
| 42 Also sometimes other users already experienced your troubles and have a | 46 Also sometimes other users already experienced your troubles and have a |
| 43 solution in hand how to circumvent a problem even if it is a bug in mplayer | 47 solution in hand how to circumvent a problem even if it is a bug in <B>MPlayer</B> |
| 44 code.<BR> | 48 code.</P> |
| 45 The language of this list is <strong>English</strong>.</P> | |
| 46 | 49 |
| 47 <P>Please describe your problem as detailed as possible with examples etc. | 50 <P>Please describe your problem as detailed as possible with examples etc. |
| 48 and do not forget to include this valuable information:</P> | 51 and do not forget to include this valuable information:</P> |
| 49 | 52 |
| 50 <P><B>What to report?</B></P> | 53 <P><B>What to report?</B></P> |
| 123 <LI>libvo/config.mak</LI> | 126 <LI>libvo/config.mak</LI> |
| 124 </UL> | 127 </UL> |
| 125 | 128 |
| 126 <P><B>For playback problems</B></P> | 129 <P><B>For playback problems</B></P> |
| 127 | 130 |
| 128 <P>Please include the output of mplayer at verbosity level 1, but remember to | 131 <P>Please include the output of <B>MPlayer</B> at verbosity level 1, but |
| 129 <B>not truncate the output</B> when you paste it into your mail. The developers need | 132 remember to <B>not truncate the output</B> when you paste it into your mail. The |
| 130 all of the messages to properly diagnose a problem. You can direct the output | 133 developers need all of the messages to properly diagnose a problem. You can |
| 131 into a file like this:</P> | 134 direct the output into a file like this:</P> |
| 132 | 135 |
| 133 <P><CODE> mplayer -v [options] [filename] &> mplayer.log</CODE></P> | 136 <P><CODE> mplayer -v [options] [filename] &> mplayer.log</CODE></P> |
| 134 | 137 |
| 135 <P>If your problem is specific to one or more files, then please upload the | 138 <P>If your problem is specific to one or more files, then please upload the |
| 136 offender(s) to:</P> | 139 offender(s) to:</P> |
| 138 <P> <A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P> | 141 <P> <A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P> |
| 139 | 142 |
| 140 <P>Also upload a small text file having the same base name as your file | 143 <P>Also upload a small text file having the same base name as your file |
| 141 with a .txt extension. Describe the problem you are having with the | 144 with a .txt extension. Describe the problem you are having with the |
| 142 particular file there and include your email address as well as the output | 145 particular file there and include your email address as well as the output |
| 143 of mplayer at verbosity level 1.<BR> | 146 of <B>MPlayer</B> at verbosity level 1.<BR> |
| 144 Usually the first 1-5 MB of a file are enough to reproduce the problem, | 147 Usually the first 1-5 MB of a file are enough to reproduce the problem, |
| 145 but to be sure we ask you to: | 148 but to be sure we ask you to: |
| 146 <P><CODE> dd if=yourfile of=smallfile bs=1024k count=5</CODE></P> | 149 <P><CODE> dd if=yourfile of=smallfile bs=1024k count=5</CODE></P> |
| 147 | 150 |
| 148 <P>It will take the first five megabytes of <STRONG>'your-file'</STRONG> and | 151 <P>It will take the first five megabytes of <STRONG>'your-file'</STRONG> and |
| 154 If the file is accessible on the net, then sending the | 157 If the file is accessible on the net, then sending the |
| 155 <STRONG>exact</STRONG> URL is sufficient.</P> | 158 <STRONG>exact</STRONG> URL is sufficient.</P> |
| 156 | 159 |
| 157 <P><B>For crashes</B></P> | 160 <P><B>For crashes</B></P> |
| 158 | 161 |
| 159 <P>If you have a core dump of the crash continue reading the next paragraph, otherwise skip it.</P> | 162 <P>If you have a core dump of the crash continue reading the next paragraph, |
| 163 otherwise skip it.</P> | |
| 160 | 164 |
| 161 <P><B>How to extract meaningful information from a core dump</B></P> | 165 <P><B>How to extract meaningful information from a core dump</B></P> |
| 162 | 166 |
| 163 <P>Please create following command file:</P> | 167 <P>Please create following command file:</P> |
| 164 | 168 |
| 175 | 179 |
| 176 <P>Then simply execute the following on your command line:</P> | 180 <P>Then simply execute the following on your command line:</P> |
| 177 <P> <CODE>gdb mplayer --core=core -batch --command=command_file > mplayer.bug</CODE></P> | 181 <P> <CODE>gdb mplayer --core=core -batch --command=command_file > mplayer.bug</CODE></P> |
| 178 | 182 |
| 179 <P><B>How to conserve information about a reproducible crash</B></P> | 183 <P><B>How to conserve information about a reproducible crash</B></P> |
| 180 <P>Re-compile mplayer with debugging code enabled:</P> | 184 <P>Recompile <B>MPlayer</B> with debugging code enabled:</P> |
| 181 <P><CODE> ./configure --enable-debug=3<BR> | 185 <P><CODE> ./configure --enable-debug=3<BR> |
| 182 make</CODE></P> | 186 make</CODE></P> |
| 183 and then run mplayer within gdb using: | 187 and then run <B>MPlayer</B> within gdb using: |
| 184 <P><CODE> gdb mplayer</CODE></P> | 188 <P><CODE> gdb mplayer</CODE></P> |
| 185 | 189 |
| 186 <P>You are now within gdb. Type:</P> | 190 <P>You are now within gdb. Type:</P> |
| 187 <P><CODE> run -v [options-to-mplayer] filename</code></P> | 191 <P><CODE> run -v [options-to-mplayer] filename</code></P> |
| 188 and reproduce your crash. As soon as you did it, gdb will | 192 and reproduce your crash. As soon as you did it, gdb will |
| 198 include only the path and filename in your bug report.</P> | 202 include only the path and filename in your bug report.</P> |
| 199 | 203 |
| 200 <P><B>I know what I am doing...</B></P> | 204 <P><B>I know what I am doing...</B></P> |
| 201 | 205 |
| 202 <P>If you created a proper bug report following the steps above and you are | 206 <P>If you created a proper bug report following the steps above and you are |
| 203 confident it is a bug in mplayer, not a compiler problem or broken file, | 207 confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken file, |
| 204 you have already read the documentation and you could not find a solution, | 208 you have already read the documentation and you could not find a solution, |
| 205 your sound drivers are OK, then you might want to subscribe to the | 209 your sound drivers are OK, then you might want to subscribe to the |
| 206 mplayer-advusers list and send your bug report there to get a better and | 210 mplayer-advusers list and send your bug report there to get a better and |
| 207 faster answer.<BR><BR> | 211 faster answer.<BR><BR> |
| 208 Please be advised that if you post newbie questions or questions answered | 212 Please be advised that if you post newbie questions or questions answered |
| 209 in the manual there, you will be ignored or flamed instead of getting an | 213 in the manual there, you will be ignored or flamed instead of getting an |
| 210 appropriate answer.<BR> | 214 appropriate answer.<BR> |
| 211 So do not flame us and subscribe to -advusers only if you really know | 215 So do not flame us and subscribe to -advusers only if you really know |
| 212 what you are doing and feel like being an advanced mplayer user or | 216 what you are doing and feel like being an advanced <B>MPlayer</B> user or |
| 213 developer. If you meet these criteria it should not be difficult to find | 217 developer. If you meet these criteria it should not be difficult to find |
| 214 out how to subscribe... | 218 out how to subscribe... |
| 215 </P> | 219 </P> |
| 216 | 220 |
| 217 </BODY> | 221 </BODY> |