[Mplayer-cvslog] CVS: main/DOCS bugreports.html,1.34,1.35
Diego Biurrun CVS
diego at mplayerhq.hu
Tue Aug 27 23:00:55 CEST 2002
- Previous message: [Mplayer-cvslog] CVS: main/DOCS codecs.html,1.80,1.81 documentation.html,1.296,1.297 encoding.html,1.62,1.63 sound.html,1.51,1.52 users_against_developers.html,1.31,1.32 video.html,1.94,1.95
- Next message: [Mplayer-cvslog] CVS: main/DOCS bugreports.html,1.35,1.36
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Update of /cvsroot/mplayer/main/DOCS
In directory mail:/var/tmp.root/cvs-serv2471
Modified Files:
bugreports.html
Log Message:
Cosmetics: Indented code and inserted empty lines.
Index: bugreports.html
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/bugreports.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- bugreports.html 4 Aug 2002 22:13:09 -0000 1.34
+++ bugreports.html 27 Aug 2002 21:00:39 -0000 1.35
@@ -15,120 +15,120 @@
<P><B>How to fix bugs</B></P>
<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>
+ 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>
<P><B>How to report bugs</B></P>
<P>First of all please try the latest CVS version of <B>MPlayer</B> as your bug
-might already be fixed there. 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
-<A HREF="documentation.html#known_bugs">the list of known bugs</A> and the rest of the
-documentation. If your problem is not known or not solvable by our instructions,
-then please report the bug.</P>
+ might already be fixed there. 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
+ <A HREF="documentation.html#known_bugs">the list of known bugs</A> and the
+ rest of the documentation. If your problem is not known or not solvable by our
+ 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>
+ 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 independent?
-Can you reproduce it with all output drivers? The more information you provide
-the better are our chances at fixing your problem. Please do not forget to
-also include the valuable information requested below, we will be unable to
-properly diagnose your problem otherwise.</P>
+ 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
+ independent? Can you reproduce it with all output drivers? The more
+ information you provide the better are our chances at fixing your problem.
+ Please do not forget to also include the valuable information requested below,
+ we will be unable to properly diagnose your problem otherwise.</P>
<P>An excellent and well written guide to asking questions in public forums is
-<A HREF="http://www.tuxedo.org/~esr/faqs/smart-questions.html">How To Ask
-Questions The Smart Way</A> by Eric S. Raymond. If you follow these guidelines
-you should be safe. But please understand that we all follow the mailing lists
-voluntarily in our free time. We are very busy and cannot guarantee that you
-will get a solution for your problem or even an answer. </P>
+ <A HREF="http://www.tuxedo.org/~esr/faqs/smart-questions.html">How To Ask
+ Questions The Smart Way</A> by Eric S. Raymond. If you follow these guidelines
+ you should be safe. But please understand that we all follow the mailing lists
+ voluntarily in our free time. We are very busy and cannot guarantee that you
+ will get a solution for your problem or even an answer.</P>
<P><B>Where to report bugs?</B></P>
<P>Subscribe to the mplayer-users mailing list:<BR>
- <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR>
-and send your bug report to:<BR>
- <A HREF="mailto:mplayer-users at mplayerhq.hu">mplayer-users at mplayerhq.hu</A></P>
+ <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR>
+ and send your bug report to:<BR>
+ <A HREF="mailto:mplayer-users at mplayerhq.hu">mplayer-users at mplayerhq.hu</A></P>
<P>The language of this list is <B>English</B>. Please follow the standard
-<A HREF="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</A> and
-<B>do not send HTML mail</B> to any of our mailing lists. You will only get
-ignored or banned. Also note that we will not individually CC (carbon-copy)
-people so it is a good idea to subscribe to actually receive your answer.</P>
+ <A HREF="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</A> and
+ <B>do not send HTML mail</B> to any of our mailing lists. You will only get
+ ignored or banned. Also note that we will not individually CC (carbon-copy)
+ people so it is a good idea to subscribe to actually receive your answer.</P>
<P><B>What to report?</B></P>
<P><B>System Information</B></P>
<UL>
-<LI>Your Linux distribution or operating system e.g.:
+ <LI>Your Linux distribution or operating system e.g.:
<UL>
- <LI>Red Hat 7.1</LI>
- <LI>Slackware 7.0 + devel packs from 7.1 ...</LI>
+ <LI>Red Hat 7.1</LI>
+ <LI>Slackware 7.0 + devel packs from 7.1 ...</LI>
</UL>
-</LI>
-<LI>kernel version:<BR>
- <CODE>uname -a</CODE></LI>
-<LI>libc version:<BR>
- <CODE>ls -l /lib/libc[.-]*</CODE></LI>
-<LI>X version:<BR>
- <CODE>X -version</CODE></LI>
-<LI>gcc and ld versions:<BR>
- <CODE>gcc -v<BR>
- ld -v</CODE></LI>
-<LI>binutils version:<BR>
- <CODE>as --version</CODE></LI>
-<LI>If you have problems with fullscreen mode:
- <UL>
- <LI>Window manager type and version</LI>
- </UL>
-</LI>
-<LI>If only the GUI is buggy:
- <UL>
- <LI>GTK version</LI>
- <LI>GLIB version</LI>
- <LI>libpng version</LI>
- <LI>GUI situation in which the bug occurs</LI>
- </UL>
-</LI>
+ </LI>
+ <LI>kernel version:<BR>
+ <CODE>uname -a</CODE></LI>
+ <LI>libc version:<BR>
+ <CODE>ls -l /lib/libc[.-]*</CODE></LI>
+ <LI>X version:<BR>
+ <CODE>X -version</CODE></LI>
+ <LI>gcc and ld versions:<BR>
+ <CODE>gcc -v<BR>
+ ld -v</CODE></LI>
+ <LI>binutils version:<BR>
+ <CODE>as --version</CODE></LI>
+ <LI>If you have problems with fullscreen mode:
+ <UL>
+ <LI>Window manager type and version</LI>
+ </UL>
+ </LI>
+ <LI>If only the GUI is buggy:
+ <UL>
+ <LI>GTK version</LI>
+ <LI>GLIB version</LI>
+ <LI>libpng version</LI>
+ <LI>GUI situation in which the bug occurs</LI>
+ </UL>
+ </LI>
</UL>
<P><B>Hardware & drivers</B></P>
<UL>
-<LI>CPU info (this works on Linux only):<BR>
+ <LI>CPU info (this works on Linux only):<BR>
<CODE>cat /proc/cpuinfo</CODE></LI>
-<LI>Video card manufacturer and model, e.g.:
+ <LI>Video card manufacturer and model, e.g.:
<UL>
- <LI>ASUS V3800U chip: nVidia TNT2 Ultra pro 32MB SDRAM</LI>
- <LI>Matrox G400 DH 32MB SGRAM</LI>
+ <LI>ASUS V3800U chip: nVidia TNT2 Ultra pro 32MB SDRAM</LI>
+ <LI>Matrox G400 DH 32MB SGRAM</LI>
</UL>
-</LI>
-<LI>Video driver type & version, e.g.:
+ </LI>
+ <LI>Video driver type & version, e.g.:
<UL>
- <LI>X built-in driver</LI>
- <LI>nVidia 0.9.623</LI>
- <LI>Utah-GLX CVS 2001-02-17</LI>
- <LI>DRI from X 4.0.3</LI>
+ <LI>X built-in driver</LI>
+ <LI>nVidia 0.9.623</LI>
+ <LI>Utah-GLX CVS 2001-02-17</LI>
+ <LI>DRI from X 4.0.3</LI>
</UL>
-</LI>
-<LI>Sound card type & driver, e.g.:
+ </LI>
+ <LI>Sound card type & driver, e.g.:
<UL>
- <LI>Creative SBLive! Gold with OSS driver from oss.creative.com</LI>
- <LI>Creative SB16 with kernel OSS drivers</LI>
- <LI>GUS PnP with ALSA OSS emulation</LI>
+ <LI>Creative SBLive! Gold with OSS driver from oss.creative.com</LI>
+ <LI>Creative SB16 with kernel OSS drivers</LI>
+ <LI>GUS PnP with ALSA OSS emulation</LI>
</UL>
-</LI>
-<LI>If in doubt include <CODE>lspci -vv</CODE> output on Linux systems.</LI>
+ </LI>
+ <LI>If in doubt include <CODE>lspci -vv</CODE> output on Linux systems.</LI>
</UL>
<P><B>For compilation problems/errors</B></P>
@@ -161,77 +161,85 @@
of <B>MPlayer</B> at verbosity level 1.<BR>
Usually the first 1-5 MB of a file are enough to reproduce the problem,
but to be sure we ask you to:
+
<P><CODE> 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
-write it to <STRONG>'small-file'</STRONG>.<BR>
-Then try again on this small file and if the bug still shows up
-your sample is sufficient for us.<BR>
-Please <STRONG>do not ever</STRONG> send such files via mail! Upload it,
-and send only the path/filename of the file on the FTP-server.<BR>
-If the file is accessible on the net, then sending the
-<STRONG>exact</STRONG> URL is sufficient.</P>
+ write it to <STRONG>'small-file'</STRONG>.<BR>
+ Then try again on this small file and if the bug still shows up
+ your sample is sufficient for us.<BR>
+ Please <STRONG>do not ever</STRONG> send such files via mail! Upload it,
+ and send only the path/filename of the file on the FTP-server.<BR>
+ If the file is accessible on the net, then sending the
+ <STRONG>exact</STRONG> URL is sufficient.</P>
<P><B>For crashes</B></P>
<P>If you have a core dump of the crash continue reading the next paragraph,
-otherwise skip it.</P>
+ otherwise skip it.</P>
<P><B>How to extract meaningful information from a core dump</B></P>
<P>Please create following command file:</P>
<P><CODE>disass $eip-32 $eip+32<BR>
-printf "eax=%08lX\n",$eax<BR>
-printf "ebx=%08lX\n",$ebx<BR>
-printf "ecx=%08lX\n",$ecx<BR>
-printf "edx=%08lX\n",$edx<BR>
-printf "esp=%08lX\n",$esp<BR>
-printf "ebp=%08lX\n",$ebp<BR>
-printf "edi=%08lX\n",$edi<BR>
-printf "esi=%08lX\n",$esi<BR>
-</CODE></P>
+ printf "eax=%08lX\n",$eax<BR>
+ printf "ebx=%08lX\n",$ebx<BR>
+ printf "ecx=%08lX\n",$ecx<BR>
+ printf "edx=%08lX\n",$edx<BR>
+ printf "esp=%08lX\n",$esp<BR>
+ printf "ebp=%08lX\n",$ebp<BR>
+ printf "edi=%08lX\n",$edi<BR>
+ printf "esi=%08lX\n",$esi<BR>
+ </CODE></P>
<P>Then simply execute the following on your command line:</P>
+
<P> <CODE>gdb mplayer --core=core -batch --command=command_file > mplayer.bug</CODE></P>
<P><B>How to conserve information about a reproducible crash</B></P>
+
<P>Recompile <B>MPlayer</B> with debugging code enabled:</P>
+
<P><CODE> ./configure --enable-debug=3<BR>
- make</CODE></P>
+ make</CODE></P>
+
and then run <B>MPlayer</B> within gdb using:
<P><CODE> gdb mplayer</CODE></P>
<P>You are now within gdb. Type:</P>
+
<P><CODE> run -v [options-to-mplayer] filename</code></P>
+
and reproduce your crash. As soon as you did it, gdb will
return you to the command line prompt where you have to enter
+
<P><CODE> bt<BR>
- disass $eip-32 $eip+32</CODE></P>
+ disass $eip-32 $eip+32</CODE></P>
+
and send the complete output to us.
<P><B>General note</B></P>
<P>If something is quite big (logs for instance) then it is better to upload
-it to the FTP server in a compressed format (gzip and bzip preferred) and
-include only the path and filename in your bug report.</P>
+ it to the FTP server in a compressed format (gzip and bzip preferred) and
+ include only the path and filename in your bug report.</P>
<P><B>I know what I am doing...</B></P>
<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>
+ 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>
- Previous message: [Mplayer-cvslog] CVS: main/DOCS codecs.html,1.80,1.81 documentation.html,1.296,1.297 encoding.html,1.62,1.63 sound.html,1.51,1.52 users_against_developers.html,1.31,1.32 video.html,1.94,1.95
- Next message: [Mplayer-cvslog] CVS: main/DOCS bugreports.html,1.35,1.36
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the MPlayer-cvslog
mailing list