Closed klemmster closed 10 years ago
h1. Reporting Bugs
If you've found a bug in libavg, please report it on the bug tracking system. It can be reached in the toolbar above ('Issues' and 'New Issue'). It will lead you to "github":https://www.github.com", and you'll need to sign up there.
Please report a bug if you hit a segmentation fault or an assertion, if make check fails on your machine, or if libavg is doing something else that it shouldn't be. If you think you might have found a bug but aren't sure, please ask in the forums. Also, please check the installation guides if you can't get libavg running at all - most causes of installation failures are described in the wiki.
h1. What to Include
To find out what is happening, we need to reproduce the bug. In the majority of cases, bug reports don't contain enough information for us to do this.
We always need to know:
If it's a configuration-related bug (many are), we need to know:
$ uname -a
$ glxinfo
h1. Segmentation Faults
If you're running into a segmentation fault, a stack trace helps:
$ gdb python
(gdb) r Test.py
[...]
./bin/bash: line 4: 4324 Segmentation fault ${dir}$tst
(gdb) bt
Replace 'Test.py' with whatever libavg program is causing the segfault. If the segfault doesn't happen directly after the 'r Test.py' line, insert a 'c' command (for 'continue'). The 'b' command should then generate your stack trace.
Done
replace textual description of how to get to issue page with actual links
https://www.libavg.de/site/projects/libavg/wiki/BugReport
depends on #20