On Thursday, 28 February 2013 16:57:04 UTC+10, Kim Burgestrand wrote:
Thanks Wayne; the problem existing because of stack/heap memory was not something that could have
occurred to me.
Technically, the problem still exists in both cases, it just shows up when using malloc, because of the way most memory allocators work. It looks like libspotify is stomping over memory it shouldn't - with stack allocated, that doesn't get detected, but it is still happening.
What made me suspect libspotify was a quick google - there are a few bug reports for libspotify on android (i.e. arm) where it is crashing on otherwise valid code.
--
---
You received this message because you are subscribed to the Google Groups "ruby-ffi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ruby-ffi+unsubscribe@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.