Mercurial > mplayer.hg
comparison DOCS/bugreports.html @ 7102:a3eefdc6e640
Added proper heading tags and fixed the HTML structure.
| author | diego |
|---|---|
| date | Tue, 27 Aug 2002 21:32:35 +0000 |
| parents | ed54a7bba268 |
| children | da10c0756649 |
comparison
equal
deleted
inserted
replaced
| 7101:ed54a7bba268 | 7102:a3eefdc6e640 |
|---|---|
| 8 </HEAD> | 8 </HEAD> |
| 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 <H1><A NAME=C>Appendix C - How to report bugs</A></H1> |
| 14 | 14 |
| 15 | 15 |
| 16 <P><B>How to fix bugs</B></P> | 16 <H2>How to fix bugs</H2> |
| 17 | 17 |
| 18 <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 |
| 19 the bug yourself. Or maybe you already did that? Please read | 19 the bug yourself. Or maybe you already did that? Please read |
| 20 <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 |
| 21 your code included in <B>MPlayer</B>. The people on the | 21 your code included in <B>MPlayer</B>. The people on the |
| 22 <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> |
| 23 mailing list will assist you if you have questions.</P> | 23 mailing list will assist you if you have questions.</P> |
| 24 | 24 |
| 25 | 25 |
| 26 <P><B>How to report bugs</B></P> | 26 <H2>How to report bugs</H2> |
| 27 | 27 |
| 28 <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 |
| 29 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 |
| 30 <A HREF="http://www.mplayerhq.hu/homepage/dload.html">this page</A> or in the | 30 <A HREF="http://www.mplayerhq.hu/homepage/dload.html">this page</A> or in the |
| 31 README. If this did not help please refer to | 31 README. If this did not help please refer to |
| 53 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 |
| 54 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 |
| 55 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> |
| 56 | 56 |
| 57 | 57 |
| 58 <P><B>Where to report bugs?</B></P> | 58 <H3>Where to report bugs?</H3> |
| 59 | 59 |
| 60 <P>Subscribe to the mplayer-users mailing list:<BR> | 60 <P>Subscribe to the mplayer-users mailing list:<BR> |
| 61 <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> |
| 62 and send your bug report to:<BR> | 62 and send your bug report to:<BR> |
| 63 <A HREF="mailto:mplayer-users@mplayerhq.hu">mplayer-users@mplayerhq.hu</A></P> | 63 <A HREF="mailto:mplayer-users@mplayerhq.hu">mplayer-users@mplayerhq.hu</A></P> |
| 67 <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 |
| 68 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) |
| 69 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 | 70 |
| 71 | 71 |
| 72 <P><B>What to report?</B></P> | 72 <H3>What to report?</H3> |
| 73 | 73 |
| 74 <P><B>System Information</B></P> | 74 <H4>System Information:</H4> |
| 75 | 75 |
| 76 <UL> | 76 <UL> |
| 77 <LI>Your Linux distribution or operating system e.g.: | 77 <LI>Your Linux distribution or operating system e.g.: |
| 78 <UL> | 78 <UL> |
| 79 <LI>Red Hat 7.1</LI> | 79 <LI>Red Hat 7.1</LI> |
| 105 </UL> | 105 </UL> |
| 106 </LI> | 106 </LI> |
| 107 </UL> | 107 </UL> |
| 108 | 108 |
| 109 | 109 |
| 110 <P><B>Hardware & drivers</B></P> | 110 <H4>Hardware & drivers:</H4> |
| 111 | 111 |
| 112 <UL> | 112 <UL> |
| 113 <LI>CPU info (this works on Linux only):<BR> | 113 <LI>CPU info (this works on Linux only):<BR> |
| 114 <CODE>cat /proc/cpuinfo</CODE></LI> | 114 <CODE>cat /proc/cpuinfo</CODE></LI> |
| 115 <LI>Video card manufacturer and model, e.g.: | 115 <LI>Video card manufacturer and model, e.g.: |
| 135 </LI> | 135 </LI> |
| 136 <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> |
| 137 </UL> | 137 </UL> |
| 138 | 138 |
| 139 | 139 |
| 140 <P><B>For compilation problems/errors</B></P> | 140 <H4>For compilation problems/errors</H4> |
| 141 | 141 |
| 142 <P><B>Please include these files:</B></P> | 142 Please include these files: |
| 143 | |
| 143 <UL> | 144 <UL> |
| 144 <LI>configure.log</LI> | 145 <LI>configure.log</LI> |
| 145 <LI>config.h</LI> | 146 <LI>config.h</LI> |
| 146 <LI>config.mak</LI> | 147 <LI>config.mak</LI> |
| 147 <LI>libvo/config.mak</LI> | 148 <LI>libvo/config.mak</LI> |
| 148 </UL> | 149 </UL> |
| 149 | 150 |
| 150 | 151 |
| 151 <P><B>For playback problems</B></P> | 152 <H4>For playback problems</H4> |
| 152 | 153 |
| 153 <P>Please include the output of <B>MPlayer</B> at verbosity level 1, but | 154 <P>Please include the output of <B>MPlayer</B> at verbosity level 1, but |
| 154 remember to <B>not truncate the output</B> when you paste it into your mail. | 155 remember to <B>not truncate the output</B> when you paste it into your mail. |
| 155 The developers need all of the messages to properly diagnose a problem. You | 156 The developers need all of the messages to properly diagnose a problem. You |
| 156 can direct the output into a file like this:</P> | 157 can direct the output into a file like this:</P> |
| 163 <P> <A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P> | 164 <P> <A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P> |
| 164 | 165 |
| 165 <P>Also upload a small text file having the same base name as your file | 166 <P>Also upload a small text file having the same base name as your file |
| 166 with a .txt extension. Describe the problem you are having with the | 167 with a .txt extension. Describe the problem you are having with the |
| 167 particular file there and include your email address as well as the output | 168 particular file there and include your email address as well as the output |
| 168 of <B>MPlayer</B> at verbosity level 1.<BR> | 169 of <B>MPlayer</B> at verbosity level 1. Usually the first 1-5 MB of a file are |
| 169 Usually the first 1-5 MB of a file are enough to reproduce the problem, | 170 enough to reproduce the problem, but to be sure we ask you to:</P> |
| 170 but to be sure we ask you to: | |
| 171 | 171 |
| 172 <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> |
| 173 | 173 |
| 174 <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 |
| 175 write it to <STRONG>'small-file'</STRONG>.<BR> | 175 write it to <STRONG>'small-file'</STRONG>. Then try again on this small file |
| 176 Then try again on this small file and if the bug still shows up | 176 and if the bug still shows up your sample is sufficient for us. Please |
| 177 your sample is sufficient for us.<BR> | 177 <STRONG>do not ever</STRONG> send such files via mail! Upload it, and send |
| 178 Please <STRONG>do not ever</STRONG> send such files via mail! Upload it, | 178 only the path/filename of the file on the FTP-server. If the file is |
| 179 and send only the path/filename of the file on the FTP-server.<BR> | 179 accessible on the net, then sending the <STRONG>exact</STRONG> URL is |
| 180 If the file is accessible on the net, then sending the | 180 sufficient.</P> |
| 181 <STRONG>exact</STRONG> URL is sufficient.</P> | 181 |
| 182 | 182 |
| 183 | 183 <H4>For crashes</H4> |
| 184 <P><B>For crashes</B></P> | |
| 185 | 184 |
| 186 <P>If you have a core dump of the crash continue reading the next paragraph, | 185 <P>If you have a core dump of the crash continue reading the next paragraph, |
| 187 otherwise skip it.</P> | 186 otherwise skip it.</P> |
| 188 | 187 |
| 189 | 188 |
| 190 <P><B>How to extract meaningful information from a core dump</B></P> | 189 <H4>How to extract meaningful information from a core dump</H4> |
| 191 | 190 |
| 192 <P>Please create following command file:</P> | 191 <P>Please create following command file:</P> |
| 193 | 192 |
| 194 <P><CODE>disass $eip-32 $eip+32<BR> | 193 <P><CODE>disass $eip-32 $eip+32<BR> |
| 195 printf "eax=%08lX\n",$eax<BR> | 194 printf "eax=%08lX\n",$eax<BR> |
| 197 printf "ecx=%08lX\n",$ecx<BR> | 196 printf "ecx=%08lX\n",$ecx<BR> |
| 198 printf "edx=%08lX\n",$edx<BR> | 197 printf "edx=%08lX\n",$edx<BR> |
| 199 printf "esp=%08lX\n",$esp<BR> | 198 printf "esp=%08lX\n",$esp<BR> |
| 200 printf "ebp=%08lX\n",$ebp<BR> | 199 printf "ebp=%08lX\n",$ebp<BR> |
| 201 printf "edi=%08lX\n",$edi<BR> | 200 printf "edi=%08lX\n",$edi<BR> |
| 202 printf "esi=%08lX\n",$esi<BR> | 201 printf "esi=%08lX\n",$esi</CODE></P> |
| 203 </CODE></P> | |
| 204 | 202 |
| 205 <P>Then simply execute the following on your command line:</P> | 203 <P>Then simply execute the following on your command line:</P> |
| 206 | 204 |
| 207 <P> <CODE>gdb mplayer --core=core -batch --command=command_file > mplayer.bug</CODE></P> | 205 <P> <CODE>gdb mplayer --core=core -batch --command=command_file > mplayer.bug</CODE></P> |
| 208 | 206 |
| 209 | 207 |
| 210 <P><B>How to conserve information about a reproducible crash</B></P> | 208 <H4>How to conserve information about a reproducible crash</H4> |
| 211 | 209 |
| 212 <P>Recompile <B>MPlayer</B> with debugging code enabled:</P> | 210 Recompile <B>MPlayer</B> with debugging code enabled: |
| 213 | 211 |
| 214 <P><CODE> ./configure --enable-debug=3<BR> | 212 <P><CODE> ./configure --enable-debug=3<BR> |
| 215 make</CODE></P> | 213 make</CODE></P> |
| 216 | 214 |
| 217 and then run <B>MPlayer</B> within gdb using: | 215 and then run <B>MPlayer</B> within gdb using: |
| 216 | |
| 218 <P><CODE> gdb mplayer</CODE></P> | 217 <P><CODE> gdb mplayer</CODE></P> |
| 219 | 218 |
| 220 <P>You are now within gdb. Type:</P> | 219 You are now within gdb. Type: |
| 221 | 220 |
| 222 <P><CODE> run -v [options-to-mplayer] filename</code></P> | 221 <P><CODE> run -v [options-to-mplayer] filename</code></P> |
| 223 | 222 |
| 224 and reproduce your crash. As soon as you did it, gdb will | 223 and reproduce your crash. As soon as you did it, gdb will |
| 225 return you to the command line prompt where you have to enter | 224 return you to the command line prompt where you have to enter |
| 228 disass $eip-32 $eip+32</CODE></P> | 227 disass $eip-32 $eip+32</CODE></P> |
| 229 | 228 |
| 230 and send the complete output to us. | 229 and send the complete output to us. |
| 231 | 230 |
| 232 | 231 |
| 233 <P><B>General note</B></P> | 232 <H3>General note</H3> |
| 234 | 233 |
| 235 <P>If something is quite big (logs for instance) then it is better to upload | 234 <P>If something is quite big (logs for instance) then it is better to upload |
| 236 it to the FTP server in a compressed format (gzip and bzip preferred) and | 235 it to the FTP server in a compressed format (gzip and bzip preferred) and |
| 237 include only the path and filename in your bug report.</P> | 236 include only the path and filename in your bug report.</P> |
| 238 | 237 |
| 239 | 238 |
| 240 <P><B>I know what I am doing...</B></P> | 239 <H2>I know what I am doing...</H2> |
| 241 | 240 |
| 242 <P>If you created a proper bug report following the steps above and you are | 241 <P>If you created a proper bug report following the steps above and you are |
| 243 confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken | 242 confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken |
| 244 file, you have already read the documentation and you could not find a | 243 file, you have already read the documentation and you could not find a |
| 245 solution, your sound drivers are OK, then you might want to subscribe to the | 244 solution, your sound drivers are OK, then you might want to subscribe to the |