History

Reporting Bugs

If you've found a bug in libavg, please report it on the bug tracking system.

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.

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:

  • The libavg version: Installer, tarball, git checkout? If git checkout: which commit and branch?
  • The exact program output.
  • If make check terminates without errors. If there are errors in make check, please sent the output of make check.

If it's a configuration-related bug (many are), we need to know:

  • What type of system you are running libavg on (OS and exact version, processor, graphics card, driver version).
  • Under Mac OS X, open the System Profiler (About This Mac -> More Info), then choose File -> Save As and RTF file format, or just tell us the version of Mac OS X as well as the model and graphics card of the computer.
  • Under linux, we need to know the distribution (incl. version) and the output of:
1$ uname -a
2$ glxinfo

Segmentation Faults

If you're running into a segmentation fault, a stack trace helps:

1 $ gdb python
2 (gdb) r Test.py
3 [...]
4 ./bin/bash: line 4:  4324 Segmentation fault      ${dir}$tst
5 (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.