Important message! Free Software under attack! See News


NOTE: bug reports and PRs are no longer being accepted. Serious inquiries for long-term collaborators may be considered, but drive by one-liners will not.

Issue Tracker

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.

NOTE: Due to frequent SPAM the issue tracker has been disabled. You can converse with other users on the mailing list or submit a bug report there. Bug reports must relate to either crashing or data corruption bugs. Feature requests, etc. are not helpful or productive and will be ignored. Patches (to fix bugs or add features or tweak existing features), however, are welcome and can be submitted as GitHub PRs or links to GIT repos/branches posted on the ML.

Before Reporting

  1. Make sure you've pulled and built the latest code--the issue you mean to report may already be fixed.
  2. Really, I mean it make sure you're running the latest code. Please do not submit bug reports for distribution packages etc. Those must go to the distributor. This bug tracker is only for issues with the live code.
  3. Find the minimum steps necessary to reproduce the issue.
  4. If the issue is a program crash or hang, then generate a backtrace.
  5. If the issue is related to project loading, please include the project files (*.non file for Non Sequencer, */history, */snapshot, */unjournaled, for Non Timeline, and */snapshot for Non Mixer)

Enabling Core Dumps

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)

Debugging a Core Dump

To start GDB from a core dump, enter a command like the following:

gdb `which non-sequencer` core

Debugging a Running Program

You can connect to the running executable by issuing a command like:

gdb `which non-mixer` `pidof non-mixer`

Enable Debugging

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
su -c './waf install'

Generating a Backtrace

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.


This work is licensed under a Creative Commons License