Closed Harvie closed 2 years ago
It is really weird. It seems that when i change the note_on line to nekobee_synth_note_on(&fSynth, 1, 1);
(different note)
I get different kind of crash. Also it does not crash when i don't call note_on at all. (keeps happily spitting silence/zeroes in that case)
This seems like a buffer overflow. Too many notes being played at once, for which there are bounds checks missing and it ends up writing past the allocated array.
Fixed in 20d62751e09c1893ea69e371e94e8cb147775eaa
Hello, i've been doing some tests and found issues in the
nekobee-src
directory. There is segmentation fault reported by gdb and even more fails reported by valgrind. (obviously, because valgrind prevents app from crashing on segv and continues executing through more subsequent segvs reporting them)Testing code (i put this in
main.c
to thenekobee-src
directory and build usinggcc -g -lm *.c -o go
):GDB backtrace:
Valgrind report: