~ubuntu-dev/mplayer/ubuntu-feisty

« back to all changes in this revision

Viewing changes to DOCS/HTML/en/bugreports_what.html

  • Committer: Reinhard Tartler
  • Date: 2006-07-08 08:47:54 UTC
  • Revision ID: siretart@tauware.de-20060708084754-c3ff228cc9c2d8de
upgrade to pre8

Show diffs side-by-side

added added

removed removed

Lines of Context:
1
 
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>B.5.�What to report</title><link rel="stylesheet" href="default.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.68.1"><link rel="start" href="index.html" title="MPlayer - The Movie Player"><link rel="up" href="bugreports.html" title="Appendix�B.�How to report bugs"><link rel="prev" href="bugreports_where.html" title="B.4.�Where to report bugs"><link rel="next" href="bugreports_advusers.html" title="B.6.�I know what I am doing..."><link rel="preface" href="howtoread.html" title="How to read this documentation"><link rel="chapter" href="intro.html" title="Chapter�1.�Introduction"><link rel="chapter" href="install.html" title="Chapter�2.�Installation"><link rel="chapter" href="usage.html" title="Chapter�3.�Usage"><link rel="chapter" href="cd-dvd.html" title="Chapter�4.�CD/DVD usage"><link rel="chapter" href="faq.html" title="Chapter�5.�Frequently Asked Questions"><link rel="chapter" href="containers.html" title="Chapter�6.�Containers"><link rel="chapter" href="codecs.html" title="Chapter�7.�Codecs"><link rel="chapter" href="video.html" title="Chapter�8.�Video output devices"><link rel="chapter" href="audio.html" title="Chapter�9.�Audio output devices"><link rel="chapter" href="tv.html" title="Chapter�10.�TV"><link rel="chapter" href="ports.html" title="Chapter�11.�Ports"><link rel="chapter" href="mencoder.html" title="Chapter�12.�Basic usage of MEncoder"><link rel="chapter" href="encoding-guide.html" title="Chapter�13.�Encoding with MEncoder"><link rel="appendix" href="mailinglists.html" title="Appendix�A.�Mailing lists"><link rel="appendix" href="bugreports.html" title="Appendix�B.�How to report bugs"><link rel="appendix" href="bugs.html" title="Appendix�C.�Known bugs"><link rel="appendix" href="skin.html" title="Appendix�D.�MPlayer skin format"><link rel="appendix" href="users-vs-dev.html" title="Appendix�E.�Developer cries"><link rel="subsection" href="bugreports_what.html#bugreports_system" title="B.5.1.�System Information"><link rel="subsection" href="bugreports_what.html#bugreports_hardware" title="B.5.2.�Hardware and drivers"><link rel="subsection" href="bugreports_what.html#bugreports_configure" title="B.5.3.�Configure problems"><link rel="subsection" href="bugreports_what.html#bugreports_conpilation" title="B.5.4.�Compilation problems"><link rel="subsection" href="bugreports_what.html#bugreports_playback" title="B.5.5.�Playback problems"><link rel="subsection" href="bugreports_what.html#bugreports_crash" title="B.5.6.�Crashes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">B.5.�What to report</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bugreports_where.html">Prev</a>�</td><th width="60%" align="center">Appendix�B.�How to report bugs</th><td width="20%" align="right">�<a accesskey="n" href="bugreports_advusers.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bugreports_what"></a>B.5.�What to report</h2></div></div></div><p>
 
1
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>B.6.�What to report</title><link rel="stylesheet" href="default.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.68.1"><link rel="start" href="index.html" title="MPlayer - The Movie Player"><link rel="up" href="bugreports.html" title="Appendix�B.�How to report bugs"><link rel="prev" href="bugreports_where.html" title="B.5.�Where to report bugs"><link rel="next" href="bugreports_advusers.html" title="B.7.�I know what I am doing..."><link rel="preface" href="howtoread.html" title="How to read this documentation"><link rel="chapter" href="intro.html" title="Chapter�1.�Introduction"><link rel="chapter" href="install.html" title="Chapter�2.�Installation"><link rel="chapter" href="usage.html" title="Chapter�3.�Usage"><link rel="chapter" href="cd-dvd.html" title="Chapter�4.�CD/DVD usage"><link rel="chapter" href="faq.html" title="Chapter�5.�Frequently Asked Questions"><link rel="chapter" href="containers.html" title="Chapter�6.�Containers"><link rel="chapter" href="codecs.html" title="Chapter�7.�Codecs"><link rel="chapter" href="video.html" title="Chapter�8.�Video output devices"><link rel="chapter" href="audio.html" title="Chapter�9.�Audio output devices"><link rel="chapter" href="tv.html" title="Chapter�10.�TV"><link rel="chapter" href="ports.html" title="Chapter�11.�Ports"><link rel="chapter" href="mencoder.html" title="Chapter�12.�Basic usage of MEncoder"><link rel="chapter" href="encoding-guide.html" title="Chapter�13.�Encoding with MEncoder"><link rel="appendix" href="mailinglists.html" title="Appendix�A.�Mailing lists"><link rel="appendix" href="bugreports.html" title="Appendix�B.�How to report bugs"><link rel="appendix" href="bugs.html" title="Appendix�C.�Known bugs"><link rel="appendix" href="skin.html" title="Appendix�D.�MPlayer skin format"><link rel="appendix" href="users-vs-dev.html" title="Appendix�E.�Developer cries"><link rel="subsection" href="bugreports_what.html#bugreports_system" title="B.6.1.�System Information"><link rel="subsection" href="bugreports_what.html#bugreports_hardware" title="B.6.2.�Hardware and drivers"><link rel="subsection" href="bugreports_what.html#bugreports_configure" title="B.6.3.�Configure problems"><link rel="subsection" href="bugreports_what.html#bugreports_compilation" title="B.6.4.�Compilation problems"><link rel="subsection" href="bugreports_what.html#bugreports_playback" title="B.6.5.�Playback problems"><link rel="subsection" href="bugreports_what.html#bugreports_crash" title="B.6.6.�Crashes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">B.6.�What to report</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bugreports_where.html">Prev</a>�</td><th width="60%" align="center">Appendix�B.�How to report bugs</th><td width="20%" align="right">�<a accesskey="n" href="bugreports_advusers.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bugreports_what"></a>B.6.�What to report</h2></div></div></div><p>
2
2
You may need to include log, configuration or sample files in your bug report.
3
3
If some of them are quite big then it is better to upload them to our
4
 
<a href="ftp://mplayerhq.hu/MPlayer/incoming/" target="_top">FTP server</a> in a
 
4
<a href="ftp://ftp.mplayerhq.hu/MPlayer/incoming/" target="_top">FTP server</a> in a
5
5
compressed format (gzip and bzip2 preferred) and include only the path and file
6
6
name in your bug report. Our mailing lists have a message size limit of 80k, if
7
7
you have something bigger you have to compress or upload it.
8
 
</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="bugreports_system"></a>B.5.1.�System Information</h3></div></div></div><p>
 
8
</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="bugreports_system"></a>B.6.1.�System Information</h3></div></div></div><p>
9
9
</p><div class="itemizedlist"><ul type="disc"><li><p>
10
10
Your Linux distribution or operating system and version e.g.:
11
11
  </p><div class="itemizedlist"><ul type="circle"><li><p>Red Hat 7.1</p></li><li><p>Slackware 7.0 + devel packs from 7.1 ...</p></li></ul></div><p>
38
38
If only the GUI is buggy:
39
39
  </p><div class="itemizedlist"><ul type="circle"><li><p>GTK version</p></li><li><p>GLIB version</p></li><li><p>libpng version</p></li><li><p>GUI situation in which the bug occurs</p></li></ul></div><p>
40
40
</p></li></ul></div><p>
41
 
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="bugreports_hardware"></a>B.5.2.�Hardware and drivers</h3></div></div></div><p>
 
41
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="bugreports_hardware"></a>B.6.2.�Hardware and drivers</h3></div></div></div><p>
42
42
</p><div class="itemizedlist"><ul type="disc"><li><p>
43
43
CPU info (this works on Linux only):
44
44
</p><pre class="screen">cat /proc/cpuinfo</pre><p>
54
54
</p></li><li><p>
55
55
If in doubt include <span><strong class="command">lspci -vv</strong></span> output on Linux systems.
56
56
</p></li></ul></div><p>
57
 
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="bugreports_configure"></a>B.5.3.�Configure problems</h3></div></div></div><p>
 
57
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="bugreports_configure"></a>B.6.3.�Configure problems</h3></div></div></div><p>
58
58
If you get errors while running <span><strong class="command">./configure</strong></span>, or autodetection
59
59
of something fails, read <tt class="filename">configure.log</tt>. You may find the
60
60
answer there, for example multiple versions of the same library mixed on your
61
61
system, or you forgot to install the development package (those with the -dev
62
62
suffix). If you think there is a bug, include <tt class="filename">configure.log</tt>
63
63
in your bug report.
64
 
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="bugreports_conpilation"></a>B.5.4.�Compilation problems</h3></div></div></div><p>
 
64
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="bugreports_compilation"></a>B.6.4.�Compilation problems</h3></div></div></div><p>
65
65
Please include these files:
66
66
</p><div class="itemizedlist"><ul type="disc"><li><p>config.h</p></li><li><p>config.mak</p></li></ul></div><p>
67
67
Only if compilation fails below one of these directories, include these files:
68
68
</p><div class="itemizedlist"><ul type="disc"><li><p>Gui/config.mak</p></li><li><p>libvo/config.mak</p></li><li><p>libao2/config.mak</p></li></ul></div><p>
69
 
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="bugreports_playback"></a>B.5.5.�Playback problems</h3></div></div></div><p>
 
69
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="bugreports_playback"></a>B.6.5.�Playback problems</h3></div></div></div><p>
70
70
Please include the output of <span class="application">MPlayer</span> at verbosity level
71
71
1, but remember to <span class="bold"><strong>not truncate the output</strong></span> when
72
72
you paste it into your mail. The developers need all of the messages to properly
74
74
</p><pre class="screen">mplayer -v <em class="replaceable"><code>options</code></em> <em class="replaceable"><code>filename</code></em> &gt; mplayer.log 2&gt;&amp;1</pre><p>
75
75
</p><p>
76
76
If your problem is specific to one or more files, then please upload the offender(s) to:
77
 
<a href="ftp://mplayerhq.hu/MPlayer/incoming/" target="_top">ftp://mplayerhq.hu/MPlayer/incoming/</a>
 
77
<a href="ftp://ftp.mplayerhq.hu/MPlayer/incoming/" target="_top">ftp://ftp.mplayerhq.hu/MPlayer/incoming/</a>
78
78
</p><p>
79
79
Also upload a small text file having the same base name as your file with a .txt
80
80
extension. Describe the problem you are having with the particular file there and
89
89
Upload it, and send only the path/filename of the file on the FTP-server. If the
90
90
file is accessible on the net, then sending the <span class="bold"><strong>exact</strong></span>
91
91
URL is sufficient.
92
 
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="bugreports_crash"></a>B.5.6.�Crashes</h3></div></div></div><p>
 
92
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="bugreports_crash"></a>B.6.6.�Crashes</h3></div></div></div><p>
93
93
You have to run <span class="application">MPlayer</span> inside <span><strong class="command">gdb</strong></span>
94
94
and send us the complete output or if you have a <tt class="filename">core</tt> dump of
95
95
the crash you can extract useful information from the Core file. Here's how:
96
 
</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="bugreports_debug"></a>B.5.6.1.�How to conserve information about a reproducible crash</h4></div></div></div><p>
 
96
</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="bugreports_debug"></a>B.6.6.1.�How to conserve information about a reproducible crash</h4></div></div></div><p>
97
97
Recompile <span class="application">MPlayer</span> with debugging code enabled:
98
98
</p><pre class="screen">
99
99
./configure --enable-debug=3
110
110
disass $pc-32 $pc+32
111
111
info all-registers
112
112
</pre><p>
113
 
</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="bugreports_core"></a>B.5.6.2.�How to extract meaningful information from a core dump</h4></div></div></div><p>
 
113
</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="bugreports_core"></a>B.6.6.2.�How to extract meaningful information from a core dump</h4></div></div></div><p>
114
114
Create the following command file:
115
115
</p><pre class="screen">
116
116
bt
119
119
</pre><p>
120
120
Then simply execute this command:
121
121
</p><pre class="screen">gdb mplayer --core=core -batch --command=<em class="replaceable"><code>command_file</code></em> &gt; mplayer.bug</pre><p>
122
 
</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bugreports_where.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="bugreports.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="bugreports_advusers.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">B.4.�Where to report bugs�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�B.6.�I know what I am doing...</td></tr></table></div></body></html>
 
122
</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bugreports_where.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="bugreports.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="bugreports_advusers.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">B.5.�Where to report bugs�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�B.7.�I know what I am doing...</td></tr></table></div></body></html>