Mercurial > mplayer.hg
comparison DOCS/bugreports.html @ 7101:ed54a7bba268
Cosmetics: Some more indents and newlines.
| author | diego |
|---|---|
| date | Tue, 27 Aug 2002 21:19:30 +0000 |
| parents | 9e641d749832 |
| children | a3eefdc6e640 |
comparison
equal
deleted
inserted
replaced
| 7100:9e641d749832 | 7101:ed54a7bba268 |
|---|---|
| 9 | 9 |
| 10 <BODY> | 10 <BODY> |
| 11 | 11 |
| 12 | 12 |
| 13 <P><B><A NAME=C>Appendix C - How to report bugs</A></B></P> | 13 <P><B><A NAME=C>Appendix C - How to report bugs</A></B></P> |
| 14 | |
| 14 | 15 |
| 15 <P><B>How to fix bugs</B></P> | 16 <P><B>How to fix bugs</B></P> |
| 16 | 17 |
| 17 <P>If you feel have the necessary skills you are invited to have a go at fixing | 18 <P>If you feel have the necessary skills you are invited to have a go at fixing |
| 18 the bug yourself. Or maybe you already did that? Please read | 19 the bug yourself. Or maybe you already did that? Please read |
| 19 <A HREF="tech/patches.txt">this short document</A> to find out how to get | 20 <A HREF="tech/patches.txt">this short document</A> to find out how to get |
| 20 your code included in <B>MPlayer</B>. The people on the | 21 your code included in <B>MPlayer</B>. The people on the |
| 21 <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</A> | 22 <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</A> |
| 22 mailing list will assist you if you have questions.</P> | 23 mailing list will assist you if you have questions.</P> |
| 24 | |
| 23 | 25 |
| 24 <P><B>How to report bugs</B></P> | 26 <P><B>How to report bugs</B></P> |
| 25 | 27 |
| 26 <P>First of all please try the latest CVS version of <B>MPlayer</B> as your bug | 28 <P>First of all please try the latest CVS version of <B>MPlayer</B> as your bug |
| 27 might already be fixed there. CVS instructions can be found at the bottom of | 29 might already be fixed there. CVS instructions can be found at the bottom of |
| 50 Questions The Smart Way</A> by Eric S. Raymond. If you follow these guidelines | 52 Questions The Smart Way</A> by Eric S. Raymond. If you follow these guidelines |
| 51 you should be safe. But please understand that we all follow the mailing lists | 53 you should be safe. But please understand that we all follow the mailing lists |
| 52 voluntarily in our free time. We are very busy and cannot guarantee that you | 54 voluntarily in our free time. We are very busy and cannot guarantee that you |
| 53 will get a solution for your problem or even an answer.</P> | 55 will get a solution for your problem or even an answer.</P> |
| 54 | 56 |
| 57 | |
| 55 <P><B>Where to report bugs?</B></P> | 58 <P><B>Where to report bugs?</B></P> |
| 56 | 59 |
| 57 <P>Subscribe to the mplayer-users mailing list:<BR> | 60 <P>Subscribe to the mplayer-users mailing list:<BR> |
| 58 <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR> | 61 <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR> |
| 59 and send your bug report to:<BR> | 62 and send your bug report to:<BR> |
| 62 <P>The language of this list is <B>English</B>. Please follow the standard | 65 <P>The language of this list is <B>English</B>. Please follow the standard |
| 63 <A HREF="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</A> and | 66 <A HREF="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</A> and |
| 64 <B>do not send HTML mail</B> to any of our mailing lists. You will only get | 67 <B>do not send HTML mail</B> to any of our mailing lists. You will only get |
| 65 ignored or banned. Also note that we will not individually CC (carbon-copy) | 68 ignored or banned. Also note that we will not individually CC (carbon-copy) |
| 66 people so it is a good idea to subscribe to actually receive your answer.</P> | 69 people so it is a good idea to subscribe to actually receive your answer.</P> |
| 70 | |
| 67 | 71 |
| 68 <P><B>What to report?</B></P> | 72 <P><B>What to report?</B></P> |
| 69 | 73 |
| 70 <P><B>System Information</B></P> | 74 <P><B>System Information</B></P> |
| 71 | 75 |
| 100 <LI>GUI situation in which the bug occurs</LI> | 104 <LI>GUI situation in which the bug occurs</LI> |
| 101 </UL> | 105 </UL> |
| 102 </LI> | 106 </LI> |
| 103 </UL> | 107 </UL> |
| 104 | 108 |
| 109 | |
| 105 <P><B>Hardware & drivers</B></P> | 110 <P><B>Hardware & drivers</B></P> |
| 106 | 111 |
| 107 <UL> | 112 <UL> |
| 108 <LI>CPU info (this works on Linux only):<BR> | 113 <LI>CPU info (this works on Linux only):<BR> |
| 109 <CODE>cat /proc/cpuinfo</CODE></LI> | 114 <CODE>cat /proc/cpuinfo</CODE></LI> |
| 128 <LI>GUS PnP with ALSA OSS emulation</LI> | 133 <LI>GUS PnP with ALSA OSS emulation</LI> |
| 129 </UL> | 134 </UL> |
| 130 </LI> | 135 </LI> |
| 131 <LI>If in doubt include <CODE>lspci -vv</CODE> output on Linux systems.</LI> | 136 <LI>If in doubt include <CODE>lspci -vv</CODE> output on Linux systems.</LI> |
| 132 </UL> | 137 </UL> |
| 138 | |
| 133 | 139 |
| 134 <P><B>For compilation problems/errors</B></P> | 140 <P><B>For compilation problems/errors</B></P> |
| 135 | 141 |
| 136 <P><B>Please include these files:</B></P> | 142 <P><B>Please include these files:</B></P> |
| 137 <UL> | 143 <UL> |
| 139 <LI>config.h</LI> | 145 <LI>config.h</LI> |
| 140 <LI>config.mak</LI> | 146 <LI>config.mak</LI> |
| 141 <LI>libvo/config.mak</LI> | 147 <LI>libvo/config.mak</LI> |
| 142 </UL> | 148 </UL> |
| 143 | 149 |
| 150 | |
| 144 <P><B>For playback problems</B></P> | 151 <P><B>For playback problems</B></P> |
| 145 | 152 |
| 146 <P>Please include the output of <B>MPlayer</B> at verbosity level 1, but | 153 <P>Please include the output of <B>MPlayer</B> at verbosity level 1, but |
| 147 remember to <B>not truncate the output</B> when you paste it into your mail. The | 154 remember to <B>not truncate the output</B> when you paste it into your mail. |
| 148 developers need all of the messages to properly diagnose a problem. You can | 155 The developers need all of the messages to properly diagnose a problem. You |
| 149 direct the output into a file like this:</P> | 156 can direct the output into a file like this:</P> |
| 150 | 157 |
| 151 <P><CODE> mplayer -v [options] [filename] &> mplayer.log</CODE></P> | 158 <P><CODE> mplayer -v [options] [filename] &> mplayer.log</CODE></P> |
| 152 | 159 |
| 153 <P>If your problem is specific to one or more files, then please upload the | 160 <P>If your problem is specific to one or more files, then please upload the |
| 154 offender(s) to:</P> | 161 offender(s) to:</P> |
| 155 | 162 |
| 156 <P> <A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P> | 163 <P> <A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P> |
| 157 | 164 |
| 158 <P>Also upload a small text file having the same base name as your file | 165 <P>Also upload a small text file having the same base name as your file |
| 159 with a .txt extension. Describe the problem you are having with the | 166 with a .txt extension. Describe the problem you are having with the |
| 160 particular file there and include your email address as well as the output | 167 particular file there and include your email address as well as the output |
| 161 of <B>MPlayer</B> at verbosity level 1.<BR> | 168 of <B>MPlayer</B> at verbosity level 1.<BR> |
| 162 Usually the first 1-5 MB of a file are enough to reproduce the problem, | 169 Usually the first 1-5 MB of a file are enough to reproduce the problem, |
| 163 but to be sure we ask you to: | 170 but to be sure we ask you to: |
| 164 | 171 |
| 165 <P><CODE> dd if=yourfile of=smallfile bs=1024k count=5</CODE></P> | 172 <P><CODE> dd if=yourfile of=smallfile bs=1024k count=5</CODE></P> |
| 166 | 173 |
| 167 <P>It will take the first five megabytes of <STRONG>'your-file'</STRONG> and | 174 <P>It will take the first five megabytes of <STRONG>'your-file'</STRONG> and |
| 168 write it to <STRONG>'small-file'</STRONG>.<BR> | 175 write it to <STRONG>'small-file'</STRONG>.<BR> |
| 171 Please <STRONG>do not ever</STRONG> send such files via mail! Upload it, | 178 Please <STRONG>do not ever</STRONG> send such files via mail! Upload it, |
| 172 and send only the path/filename of the file on the FTP-server.<BR> | 179 and send only the path/filename of the file on the FTP-server.<BR> |
| 173 If the file is accessible on the net, then sending the | 180 If the file is accessible on the net, then sending the |
| 174 <STRONG>exact</STRONG> URL is sufficient.</P> | 181 <STRONG>exact</STRONG> URL is sufficient.</P> |
| 175 | 182 |
| 183 | |
| 176 <P><B>For crashes</B></P> | 184 <P><B>For crashes</B></P> |
| 177 | 185 |
| 178 <P>If you have a core dump of the crash continue reading the next paragraph, | 186 <P>If you have a core dump of the crash continue reading the next paragraph, |
| 179 otherwise skip it.</P> | 187 otherwise skip it.</P> |
| 188 | |
| 180 | 189 |
| 181 <P><B>How to extract meaningful information from a core dump</B></P> | 190 <P><B>How to extract meaningful information from a core dump</B></P> |
| 182 | 191 |
| 183 <P>Please create following command file:</P> | 192 <P>Please create following command file:</P> |
| 184 | 193 |
| 195 | 204 |
| 196 <P>Then simply execute the following on your command line:</P> | 205 <P>Then simply execute the following on your command line:</P> |
| 197 | 206 |
| 198 <P> <CODE>gdb mplayer --core=core -batch --command=command_file > mplayer.bug</CODE></P> | 207 <P> <CODE>gdb mplayer --core=core -batch --command=command_file > mplayer.bug</CODE></P> |
| 199 | 208 |
| 209 | |
| 200 <P><B>How to conserve information about a reproducible crash</B></P> | 210 <P><B>How to conserve information about a reproducible crash</B></P> |
| 201 | 211 |
| 202 <P>Recompile <B>MPlayer</B> with debugging code enabled:</P> | 212 <P>Recompile <B>MPlayer</B> with debugging code enabled:</P> |
| 203 | 213 |
| 204 <P><CODE> ./configure --enable-debug=3<BR> | 214 <P><CODE> ./configure --enable-debug=3<BR> |
| 216 | 226 |
| 217 <P><CODE> bt<BR> | 227 <P><CODE> bt<BR> |
| 218 disass $eip-32 $eip+32</CODE></P> | 228 disass $eip-32 $eip+32</CODE></P> |
| 219 | 229 |
| 220 and send the complete output to us. | 230 and send the complete output to us. |
| 231 | |
| 221 | 232 |
| 222 <P><B>General note</B></P> | 233 <P><B>General note</B></P> |
| 223 | 234 |
| 224 <P>If something is quite big (logs for instance) then it is better to upload | 235 <P>If something is quite big (logs for instance) then it is better to upload |
| 225 it to the FTP server in a compressed format (gzip and bzip preferred) and | 236 it to the FTP server in a compressed format (gzip and bzip preferred) and |
| 226 include only the path and filename in your bug report.</P> | 237 include only the path and filename in your bug report.</P> |
| 238 | |
| 227 | 239 |
| 228 <P><B>I know what I am doing...</B></P> | 240 <P><B>I know what I am doing...</B></P> |
| 229 | 241 |
| 230 <P>If you created a proper bug report following the steps above and you are | 242 <P>If you created a proper bug report following the steps above and you are |
| 231 confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken | 243 confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken |