| 1 |
# Reporting Bugs |
| 2 |
- Make sure you're using the latest release. |
| 3 |
- If possible, also check if the problem has already been fixed in git master. |
| 4 |
- Don't report multiple unrelated/barely related bugs in one issue. |
| 5 |
- Attach a log file. |
| 6 |
- You can make Celluloid print log messages by running |
| 7 |
`G_MESSAGES_DEBUG=all celluloid --mpv-msg-level=all=trace` |
| 8 |
- The command above will cause Celluloid to generate a large amount of |
| 9 |
log messages, so you may also want to redirect the output to a file. |
| 10 |
For example, you can redirect log messages to `/tmp/celluloid.log` |
| 11 |
with this command: |
| 12 |
`G_MESSAGES_DEBUG=all celluloid --mpv-msg-level=all=trace &> /tmp/celluloid.log`. |
| 13 |
- If the issue involves crashing, include a backtrace in the report. |
| 14 |
- You can create a backtrace by running |
| 15 |
`gdb -ex 'set pagination off' -ex run -ex bt celluloid` |
| 16 |
and perform the action that triggers the crash. |
| 17 |
- If the issue is a regression, it would be very helpful if you could perform a |
| 18 |
[bisect](https://git-scm.com/docs/git-bisect) to locate the commit that |
| 19 |
introduces the regression. |