search

danomatika / ofxMidi

(maintained) Midi addon for openFrameworks
Other
262 stars 73 forks source link

EXC_BAD_ACCESS #5

Closed erinnovations closed 12 years ago

erinnovations commented 13 years ago

I tried the input sample and it is always crashes when I try to push something on my m-Audio TriggerFinger. I'm on 10.6.6 OSX.

The EXC_BAD_ACCESS happening at iostream:77: static ios_base::Init __ioinit;

XCode log:

[Session started at 2011-11-04 11:09:40 +0100.] GNU gdb 6.3.50-20050815 (Apple version gdb-1469) (Wed May 5 04:36:56 UTC 2010) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-apple-darwin".tty /dev/ttys000 Loading program into debugger… Program loaded. run [Switching to process 3994] Running… ofxMidiIn: 2 ports available 0: USB Trigger Finger 1: ipMIDI Port 1 [Switching to process 3994] Program received signal: “EXC_BAD_ACCESS”. [Switching to process 3994] sharedlibrary apply-load-rules all (gdb)

chrisoshea commented 13 years ago

This is hard for me to test.

Is it happening during setup() or when your push something on your midi device?

If your setup code looks like this:

printf("do list ports\n");
midiIn.listPorts();

printf("try open port\n");
midiIn.openPort(0);

does it crach on openPort?

bilderbuchi commented 13 years ago

can you show a stacktrace or some more info about where exactly the error is thrown? more specifically, at what place in the ofxMidi code? iostream is a built-in functions, so we need to see which part fo ofxMidi called that function, the culprit is probably there. probably a problem with the code trying to access data which isn't there/out of bounds arrays/whatever.

erinnovations commented 13 years ago

I see the list of the devices in the console and I think it connects to the device right because if I not push anything there is no error. The error is suddenly happens if I try to do something on the controller.

I will try to find where is the call if I will have some time.

danomatika commented 12 years ago

You you try again using the updates in the develop branch? If not, can you close this issue?