Libav starting tasks: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Dark Shikari (talk | contribs) (→QA) |
||
| Line 4: | Line 4: | ||
===QA=== | ===QA=== | ||
(TODO: make this a bit more detailed so it doesn't require as much searching/knowledge to do.) | |||
Finding bugs in libav is always welcome, and requires little to no knowledge of libav itself. Here's one possible process: | |||
* Make a build of libav with debug symbols. | |||
* Download a sample file from the samples archive. | |||
* Download zzuf and use it to fuzz libav on the file. | |||
* When you find a crash, do a gdb backtrace and report the bug to the libav bug tracker following the bug tracker guidelines. | |||
If a sample file doesn't seem to be giving any crashes, try a different one. Some decoders are more buggy than others. | |||
===Documentation=== | ===Documentation=== | ||
Revision as of 04:02, 4 September 2011
Want to get started doing something useful in libav, but not sure where to start? Here's some basic tasks you can do that don't require much detailed knowledge of libav's internals. Need help? Ask on IRC and someone can answer questions and help walk you through your task of choice.
Task categories
QA
(TODO: make this a bit more detailed so it doesn't require as much searching/knowledge to do.)
Finding bugs in libav is always welcome, and requires little to no knowledge of libav itself. Here's one possible process:
- Make a build of libav with debug symbols.
- Download a sample file from the samples archive.
- Download zzuf and use it to fuzz libav on the file.
- When you find a crash, do a gdb backtrace and report the bug to the libav bug tracker following the bug tracker guidelines.
If a sample file doesn't seem to be giving any crashes, try a different one. Some decoders are more buggy than others.