Appendix C - How to report bugs

How to report bugs?

First of all please try the latest CVS version of mplayer as your bug might already be fixed there. CVS instructions can be found at the bottom of this page.

If this did not help please refer to Appendix D and the rest of the documentation. If your problem is not known or not solvable by our instructions, then please report the bug.

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 this short document to find out how to get your code included in mplayer. The people on the mplayer-dev-eng mailing list can assist you if you have questions.

Where to report bugs?

Subscribe to the mplayer-users mailing list:
    http://mplayerhq.hu/mailman/listinfo/mplayer-users
and send your bug report to:
    mplayer-users@mplayerhq.hu
Please note that we will not individually CC (carbon-copy) people so it is a good idea to subscribe to actually receive your answer.

Please do not send bug reports privately to individual developers. This is community work and thus there might be several people interested in it. Also sometimes other users already experienced your troubles and have a solution in hand how to circumvent a problem even if it is a bug in mplayer code.
The language of this list is English.

Please describe your problem as detailed as possible with examples etc. and do not forget to include this valuable information:

What to report?

System Information

• Your Linux distribution or operating system e.g.:
  • Red Hat 7.1
  • Slackware 7.0 + devel packs from 7.1 ...
• kernel version:
  uname -a
• libc version:
  ls -l /lib/libc[.-]*
• X version:
  X -version
• gcc and ld versions:
  gcc -v
ld -v
• binutils version:
  as --version
• If you have problems with fullscreen mode:
  • Window manager type and version
• If only the GUI is buggy:
  • GTK version
  • GLIB version
  • libpng version
  • GUI situation in which the bug occurs

Hardware & drivers

• CPU info (this works on Linux only):
  cat /proc/cpuinfo
• Video card manufacturer and model, e.g.:
  • ASUS V3800U chip: nVidia TNT2 Ultra pro 32MB SDRAM
  • Matrox G400 DH 32MB SGRAM
• Video driver type & version, e.g.:
  • X built-in driver
  • nVidia 0.9.623
  • Utah-GLX CVS 2001-02-17
  • DRI from X 4.0.3
• Sound card type & driver, e.g.:
  • Creative SBLive! Gold with OSS driver from oss.creative.com
  • Creative SB16 with kernel OSS drivers
  • GUS PnP with ALSA OSS emulation
• If in doubt include lspci -vv output on Linux systems.

For compilation problems/errors

Please include these files:

• configure.log
• config.h
• config.mak
• libvo/config.mak

For playback problems

Please include the output of mplayer at verbosity level 1, but remember to not truncate the output when you paste it into your mail. The developers need all of the messages to properly diagnose a problem. You can direct the output into a file like this:

    mplayer -v [options] [filename] &> mplayer.log

If your problem is specific to one or more files, then please upload the offender(s) to:

    ftp://mplayerhq.hu/MPlayer/incoming/

Also upload a small text file having the same base name as your file with a .txt extension. Describe the problem you are having with the particular file there and include your email address as well as the output of mplayer at verbosity level 1.
Usually the first 1-5 MB of a file are enough to reproduce the problem, but to be sure we ask you to:

    dd if=yourfile of=smallfile bs=1024k count=5

It will take the first five megabytes of 'your-file' and write it to 'small-file'.
Then try again on this small file and if the bug still shows up your sample is sufficient for us.
Please do not ever send such files via mail! Upload it, and send only the path/filename of the file on the FTP-server.
If the file is accessible on the net, then sending the exact URL is sufficient.

For crashes

If you have a core dump of the crash continue reading the next paragraph, otherwise skip it.

How to extract meaningful information from a core dump

Please create following command file:

disass $eip-32 $eip+32
printf "eax=%08lX\n",$eax
printf "ebx=%08lX\n",$ebx
printf "ecx=%08lX\n",$ecx
printf "edx=%08lX\n",$edx
printf "esp=%08lX\n",$esp
printf "ebp=%08lX\n",$ebp
printf "edi=%08lX\n",$edi
printf "esi=%08lX\n",$esi


Then simply execute the following on your command line:

    gdb mplayer --core=core -batch --command=command_file > mplayer.bug

How to conserve information about a reproducible crash

Re-compile mplayer with debugging code enabled:

    ./configure --enable-debug=3
    make

    gdb mplayer

You are now within gdb. Type:

    run -v [options-to-mplayer] filename

    bt
    disass $eip-32 $eip+32

General note

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.

I know what I am doing...

If you created a proper bug report following the steps above and you are confident it is a bug in mplayer, 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.

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.
So do not flame us and subscribe to -advusers only if you really know what you are doing and feel like being an advanced mplayer user or developer. If you meet these criteria it should not be difficult to find out how to subscribe...