I still haven't been able to figure out what causes the INVALID HEAP ADDRESS error.
I though it was introduced after the 5.02 release, but it turned out that I can actually reproduce it with all 5.0x releases. Unfortunately, I need the new Motor library so I cannot use the previous 4.0 release; which ironically works perfectly fine. It's not a cable issue since I get the same error with 3 good quality cables that I've successfully used before, but no errors with 4.0. I have two(2) identical Nexus S devices with the original manufacture Android 4.1.2 release (no rooter). I have used both of them before with 4.0 and no problems either. The tricky part is that everything works fine while the app is launched for the first since the exception doesn't occur until you exit the app and it tries to close the Bluetooth socket. After that the device has problems trying to connect to the IOIO again. Here is the basic use-case: >From Eclipse Juno, Kepler, or Luna; launch the IOIOSimpleApp. The laptop is connected to the Nexus S via an USB cable and the device communicates with the IOIO-OTG via Bluetooth. Turn the LED on and off to confirm it is communicating with the IOIO. Then, exit the app and I get the errors below. 08-08 19:08:32.678: A/libc(17962): @@@ ABORTING: INVALID HEAP ADDRESS IN dlfree addr=0x515e7268 08-08 19:08:32.678: A/libc(17962): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 17962 (examples.simple) -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
