On Wed, 03 Aug 2011 07:45:56 +0000, Ralf Mattes wrote:
> Hello list,
>
> after a git-pull (and autoreconf -vfi) denemo builds but fails to run:
>
> Any ideas?
>
Some desperate debugging later ...
Seems like denemo just segfaults (now: why don't I see this at the shell prompt?
Is someone really catching signals?).
Stacktrace is here:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb687f730 (LWP 19947)]
jack_output_midi_event (buffer=0xbfe7e44b "ð\177\177\b\b\003\177\177", '@'
<repeats 12 times>, "÷", client_number=0, port_number=0)
at jackmidi.c:187
warning: Source file is more recent than executable.
187 DenemoScore *si = Denemo.gui->si;
(gdb)
Now:
(gdb) print Denemo.gui
$1 = (DenemoGUI *) 0x0
Dereferencing this like here ' DenemoScore *si = Denemo.gui->si; ' of course
segfaults.
BTW - why does denemo try to set/change the tuning _during startup_???
#1 0x0808a9d2 in change_tuning (cents=0x81653c0) at midi.c:135
#2 0x0810a64f in set_tuning () at pitchentry.c:1103
That's a nuisance at least. Keep of my keyboard unless i ask you for it.
(And it's silly on so many levels: midi might not be connected, my excellent
organ
simulator (Aeolus) doesn't care about tuning messages ....).
Cheers, RalfD
> Cheers, RalfD
_______________________________________________
Denemo-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/denemo-devel
