User Tools

Site Tools


general:bugtracker

This is an old revision of the document!


Reporting bugs

Please report bugs in the Avidemux forums to get some feedback and determine the nature of the problem.

If it involves non systematic crashes, please also do the following:

gdb avidemux2
r

Do as you usual, when it crashes, go back to gdb and take the output of

bt

That plus the last lines printed by avidemux2 will help a lot.

Bug reporting for newcomers

  • Before opening a thread about a problem, search the forum and read this Wiki, especially the FAQ. Chances are someone might have noticed that bug before you. It might have been fixed or a workaround may have been advised until the fix gets commited. It is also possible what you're seeing isn't an actual bug but results from bad manipulation of avidemux on your behalf. Also, make sure you're using the very latest version. Whatever version you're using, please mention it. The FAQ has an entry to help you determine the precise revision number if you don't know.
  • Thoroughly describe the steps that will reproduce the bug.
  • If the bug is specific to a certain input file or a certain input file format, cut a short sample that exhibits the problem and upload it to a free file hosting service. Also post a MediaInfo report about the input file.
  • In all cases, post the Avidemux log file. It is located in %APPDATA%/avidemux/admlog.txt on Windows and in ~/.avidemux/admlog.txt on Linux (or in the console, if you ran it from there).

Posting log files

You can use pastebin or pastebay to post large text content. Posting in the thread itself is of course allowed but makes reading the thread painful, and could turn some helpers away.

Posting samples

The avidemux project doesn't provide storage for the samples you may send. Many free file hosting services exist for that purpose. Here are a couple you may use :

(To be added : a short paragraph on cutting)

general/bugtracker.1271771294.txt.gz · Last modified: 2012/11/11 08:51 (external edit)