Stefan Sauer

Hi, if you still have the version from the ubuntu software center installed, couly you run it via `gdb /usr/bin/buzztrax-edit` and when it crashed type `bt` to get a stacktrace?...

Thanks, the key points are """ (buzztrax-edit:3165): Gtk-WARNING **: 00:52:47.826: ../../../../gtk/gtktreemodel.c:1794: Invalid column number 4 accessed (remember to end your list of columns with a -1) free(): invalid pointer """...

Hi, did you had a change to try the git version. There is a chat in https://gitter.im/Buzztrax/buzztrax if you need help with compiling. With a version from git we can...

It seems that the binaries you built crash right away :/ If you run this from your build dir: ``` G_DEBUG="fatal_warnings" libtool --mode=execute gdb --args ./buzztrax-cmd --command=play --input-file=tests/songs/test-simple1.xml ``` this...

Maybe don't activate '-Werror=misleading-indentation' if that causes build errors. This is apparently a new gcc warning and it is a bit silly.

I added a travis build for without --enable-debug and it passes: https://travis-ci.org/Buzztrax/buzztrax/jobs/140203433

Thanks for keeping testing. Crash should be prevented by the test setup (See https://github.com/Buzztrax/buzztrax/blob/master/Makefile.tests.am#L45). There is a strange design designing in gsetting, where one function in glib crashes is the...

The uninstalled tests should now work, running a test directly would need to be changed and set even more envvars: ``` GSETTINGS_BACKEND=memory GSETTINGS_SCHEMA_DIR=$PWD LC_ALL=C G_DEBUG="fatal_warnings" libtool --mode=execute gdb --args ./buzztrax-cmd...

Yes that is helpful: this one is flaky (it mostly passes), there is probably some race: tests/lib/core/e-sequence.c:457:F:BtSequenceExamples:test_bt_sequence_ticks:0: Assertion 'data.values[1] == 1' failed: data.values[1] == 0, 1 == 1 I just...

Sorry, pushed the wrong file previously.