comparison DOCS/bugreports.html @ 6387:26c35aa7e1d8

Remind people to NOT cut mplayer output, removed italics that make text hard to read on a screen + minor fixes.
author diego
date Tue, 11 Jun 2002 18:57:47 +0000
parents 3ca1f8cf7bfc
children 4e5c236ade69
comparison
equal deleted inserted replaced
6386:039065ac8625 6387:26c35aa7e1d8
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1 <HTML> 2 <HTML>
2 3
3 <HEAD> 4 <HEAD>
4 <STYLE> 5 <STYLE TYPE="text/css">
5 .text 6 .text
6 {font-family : Verdana, Arial, Helvetica, sans-serif; 7 {font-family : Verdana, Arial, Helvetica, sans-serif;
7 font-size : 14px;} 8 font-size : 14px;}
8 </STYLE> 9 </STYLE>
9 </HEAD> 10 </HEAD>
43 <P>Please describe your problem as detailed as possible with examples etc. 44 <P>Please describe your problem as detailed as possible with examples etc.
44 and do not forget to include this valuable information:</P> 45 and do not forget to include this valuable information:</P>
45 46
46 <P><B>What to report?</B></P> 47 <P><B>What to report?</B></P>
47 48
48 <P><B><I>System Information</I></B></P> 49 <P><B>System Information</B></P>
49 50
50 <UL> 51 <UL>
51 <LI>Your Linux distribution or operating system e.g.: 52 <LI>Your Linux distribution or operating system e.g.:
52 <UL> 53 <UL>
53 <LI>Red Hat 7.1</LI> 54 <LI>Red Hat 7.1</LI>
78 <LI>GUI situation in which the bug occurs</LI> 79 <LI>GUI situation in which the bug occurs</LI>
79 </UL> 80 </UL>
80 </LI> 81 </LI>
81 </UL> 82 </UL>
82 83
83 <P><B><I>Hardware &amp; drivers</I></B></P> 84 <P><B>Hardware &amp; drivers</B></P>
84 85
85 <UL> 86 <UL>
86 <LI>CPU info (this works on Linux only):<BR> 87 <LI>CPU info (this works on Linux only):<BR>
87 <CODE>cat /proc/cpuinfo</CODE></LI> 88 <CODE>cat /proc/cpuinfo</CODE></LI>
88 <LI>Video card manufacturer and model, e.g.: 89 <LI>Video card manufacturer and model, e.g.:
109 <LI>If in doubt include <CODE>lspci -vv</CODE> output on Linux systems.</LI> 110 <LI>If in doubt include <CODE>lspci -vv</CODE> output on Linux systems.</LI>
110 </UL> 111 </UL>
111 112
112 <P><B>For compilation problems/errors</B></P> 113 <P><B>For compilation problems/errors</B></P>
113 114
114 <P><B><I>Please include these files:</I></B></P> 115 <P><B>Please include these files:</B></P>
115 <UL> 116 <UL>
116 <LI>configure.log</LI> 117 <LI>configure.log</LI>
117 <LI>config.h</LI> 118 <LI>config.h</LI>
118 <LI>config.mak</LI> 119 <LI>config.mak</LI>
119 <LI>libvo/config.mak</LI> 120 <LI>libvo/config.mak</LI>
120 </UL> 121 </UL>
121 122
122 <P><B>For playback problems</B></P> 123 <P><B>For playback problems</B></P>
123 124
124 <P><B><I>Please include the output of mplayer at verbosity level 1</I></B></P> 125 <P>Please include the output of mplayer at verbosity level 1, but remember to
125 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;mplayer -v [options] filename &amp;&gt; mplayer.log</CODE></P> 126 <B>not cut the output</B> when you paste it into your mail. The developers need
127 all of the messages to properly diagnose a problem. You can direct the output
128 into a file like this:</P>
129
130 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;mplayer -v [options] [filename] &amp;&gt; mplayer.log</CODE></P>
126 131
127 <P>If your problem is specific to one or more files, then please upload the 132 <P>If your problem is specific to one or more files, then please upload the
128 offender(s) to:</P> 133 offender(s) to:</P>
129 134
130 <P>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P> 135 <P>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P>
144 Please <STRONG>do not ever</STRONG> send such files via mail! Upload it, 149 Please <STRONG>do not ever</STRONG> send such files via mail! Upload it,
145 and send only the path/filename of the file on the FTP-server.<BR> 150 and send only the path/filename of the file on the FTP-server.<BR>
146 If the file is accessible on the net, then sending the 151 If the file is accessible on the net, then sending the
147 <STRONG>exact</STRONG> URL is sufficient.</P> 152 <STRONG>exact</STRONG> URL is sufficient.</P>
148 153
149 <P><B><I>For crashes</I></B></P> 154 <P><B>For crashes</B></P>
150 155
151 <P><I>If you have a core dump of the crash continue reading the next paragraph, otherwise skip it.</I></P> 156 <P>If you have a core dump of the crash continue reading the next paragraph, otherwise skip it.</P>
152 157
153 <P><B><I>How to extract meaningful information from a core dump</I></B></P> 158 <P><B>How to extract meaningful information from a core dump</B></P>
154 159
155 <P>Please create following command file:</P> 160 <P>Please create following command file:</P>
156 161
157 <P><CODE>disass $eip-32 $eip+32<BR> 162 <P><CODE>disass $eip-32 $eip+32<BR>
158 printf "eax=%08lX\n",$eax<BR> 163 printf "eax=%08lX\n",$eax<BR>
166 </CODE></P> 171 </CODE></P>
167 172
168 <P>Then simply execute the following on your command line:</P> 173 <P>Then simply execute the following on your command line:</P>
169 <P>&nbsp;&nbsp;&nbsp;&nbsp;<CODE>gdb mplayer --core=core -batch --command=command_file &gt; mplayer.bug</CODE></P> 174 <P>&nbsp;&nbsp;&nbsp;&nbsp;<CODE>gdb mplayer --core=core -batch --command=command_file &gt; mplayer.bug</CODE></P>
170 175
171 <P><B><I>How to conserve information about a reproducible crash</I></B></P> 176 <P><B>How to conserve information about a reproducible crash</B></P>
172 <P>Re-compile mplayer with debugging code enabled:</P> 177 <P>Re-compile mplayer with debugging code enabled:</P>
173 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;./configure --enable-debug=3<BR> 178 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;./configure --enable-debug=3<BR>
174 &nbsp;&nbsp;&nbsp;&nbsp;make</CODE></P> 179 &nbsp;&nbsp;&nbsp;&nbsp;make</CODE></P>
175 and then run mplayer within gdb using: 180 and then run mplayer within gdb using:
176 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;gdb mplayer</CODE></P> 181 <P><CODE>&nbsp;&nbsp;&nbsp;&nbsp;gdb mplayer</CODE></P>
184 and send the complete output to us. 189 and send the complete output to us.
185 190
186 <P><B>General note</B></P> 191 <P><B>General note</B></P>
187 192
188 <P>If something is quite big (logs for instance) then it is better to upload 193 <P>If something is quite big (logs for instance) then it is better to upload
189 it to the FTP-server in a compressed format (gzip and bzip preferred) and 194 it to the FTP server in a compressed format (gzip and bzip preferred) and
190 include only the path and filename in your bug report.</P> 195 include only the path and filename in your bug report.</P>
191 196
192 <P><B>I know what I am doing...</B></P> 197 <P><B>I know what I am doing...</B></P>
193 198
194 <P>If you created a proper bug report following the steps above and you are 199 <P>If you created a proper bug report following the steps above and you are