On Mar 4, 10:16 pm, Bob Kerns <[email protected]> wrote: > I've seen Dalvik give a Verify error in cases where I'd expect a > NoSuchMethodError. That is, it calls a method that was there when the > code was compiled, but at runtime, the version of the class it found > did not have that method.
This changed in 2.x. In 1.6 and earlier the VM throws a VerifyError and abandons the entire class, in 2.0 and later it inserts "always throw" instructions and lets nature take its course. > Running under the debugger and breaking on exceptions may give you > more clues than logcat. The logcat output for a VerifyError is pretty detailed, as far as telling you what the VM doesn't like. What it doesn't give you is a stack trace that shows you how you get to the code that uses the method in question, which can be useful too. -- 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
