On Sep 9, 11:59 am, DaveG <[email protected]> wrote: > Ah, yeah, forgot about building it myself, duh. Ok, with symbols, it > becomes > clear that System.gc() is running (triggered by a JNI call up to Java) > and > is barfing on something it finds, likely because of an invalid > DeleteLocalRef() > call in my C code somewhere. That should be easy enough to find.
An invalid DeleteLocalRef should cause the CheckJNI code to scream. And probably not cause a failure due to the way local refs are currently implemented. In my experience, crashes during GC are often the result of something scribbling on the virtual heap. The "forcecopy" mode of CheckJNI can find some of these (instead of returning a raw pointer to primitive arrays on the virtual heap, it makes a copy wrapped in guard pages, so anything that runs off the start/end gets spotted early). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
