2.4 Reporting Bugs

Any problems with the installation should be reported to bug-guile@gnu.org.

If you find a bug in G-Wrap, please report it to the Guile developers, so they can fix it. When you write a bug report, please make sure to include as much of the information described below in the report. If you can’t figure out some of the items, it is not a problem, but the more information we get, the more likely we can diagnose and fix the bug.

• The version number of G-Wrap. This manual documents G-Wrap version 1.9.15.
• The version number of Guile. You can get this information from invoking ‘guile --version’ at your shell, or calling (version) from within Guile.
• A complete description of how to reproduce the bug.

  If you have a Scheme program that produces the bug, please include it in the bug report. If your program is too big to include. please try to reduce your code to a minimal test case.

• A description of the incorrect behavior. For example, "The Guile process gets a fatal signal," or, "The resulting output is as follows, which I think is wrong."

  If the manifestation of the bug is a Guile error message, it is important to report the precise text of the error message, and a backtrace showing how the Scheme program arrived at the error. This can be done using the ,backtrace command in Guile’s debugger.

If your bug causes Guile to crash, additional information from a low-level debugger such as GDB might be helpful. If you have built Guile yourself, you can run Guile under GDB via the meta/gdb-uninstalled-guile script. Instead of invoking Guile as usual, invoke the wrapper script, type run to start the process, then backtrace when the crash comes. Include that backtrace in your report.