Checklist

When writing your bug report, please include:

• What you were trying to accomplish (e.g., "I am trying to transcode from this format to that format...")
• The problem you encountered (e.g., "avconv crashed" or "The output video was all green")
• The exact command line you were using (e.g., "avconv -i input.mov -an -c:v foo output.avi")
• The full, uncut console output provided by avconv -v 9 -loglevel 99 -i followed by the name of your input file (copy/pasted from the console, including the banner that indicates version and configuration options), paste avplay output only if your problem is not reproducible with avconv.

If you encounter a crash bug, please provide the gdb output, backtrace and disassembly using an unstripped avconv binary as follows:

gdb avconv

In gdb, type 'r' for run, along with the rest of the avconv command line:

r <rest of command line>

When gdb encounters its problem, run the following commands and copy/paste the output into your bug report:

bt
disass $pc-32,$pc+32
info all-registers

For gdb versions before 7.1, you need to employ a slightly different syntax for the above disass command:

disass $pc-32 $pc+32

If gdb does not provide useful information please try to use Valgrind to trace possible memory corruption.

valgrind avconv <rest of command line>

Once you have gathered this information, you can submit a report to the Libav bug tracker. You should provide all information so that anyone can reproduce the bug.

Submitting Sample Media

The developers may ask you to provide a sample media file illustrating your problem. In this case, please follow these steps:

• If the sample file is too large ( > 10 megabytes), cut it down to size with the Unix 'dd' command:

  dd if=sample-file of=small-sample-file bs=1024 count=10000

  and then upload small-sample-file rather than sample-file
• Please choose descriptive names like "h264_green_tint.mov" or "block_artifacts_after_seeking.mkv". We already have plenty of "bug.rm" and "sample.avi" to choose from.
• Upload the sample to the Libav FTP server. Note that our FTP server is write-only in order to prevent abuses. Do not let this confuse you. Even though you cannot see the file you uploaded, it will be there and the Libav developers will have access.
  • Log into upload.libav.org with an anonymous FTP login.
  • cd -> incoming
  • Create a new directory.
  • cd -> your new directory
  • Upload a brief text file describing the sample and what is wrong. This is important! If you leave out the text file it would be harder for us to figure out where to archive it.
  • Upload the sample.
• Email the list and indicate the location of the sample.