- IRC #non at irc.freenode.net
The issue tracker for Non can be found at github. Please specify which program you encountered an error in, and give as much detail as possible in your report. Use the following guide for reporting bugs.
If the issue is a program crash, then you should enable core dumps by running the following command from the shell you intend to invoke the crashing program from
ulimit -c unlimited
After a segmentation fault, a file named 'core' will be left in the directory the program was running from (this is usually the project directory)
To start GDB from a core dump, enter a command like the following:
gdb `which non-sequencer` core
You can connect to the running executable by issuing a command like:
gdb `which non-mixer` `pidof non-mixer`
In order to capture a meaningful backtrace, NTK and Non must be built with debugging symbols. Use --enable-debug argument to ./waf configure like so:
./waf configure --enable-debug ./waf su -c './waf install'
To generate a full backtrace, enter the following at the gdb command prompt:
set logging on thread apply all bt full
GDB will write to a log file called gdb.txt. You can attach this to an email or bug report or use a tool such as KX Studio Paste to share it on IRC.
This work is licensed under a Creative Commons License