On Feb 10, 6:35 pm, sdphil <[email protected]> wrote: > 02-10 18:31:52.229: WARN/dalvikvm(10604): VFY: copyRes1 v0<-v7 cat=3 > type=2 > 02-10 18:31:52.229: WARN/dalvikvm(10604): VFY: rejecting opcode 0x0c > at 0x0045 > 02-10 18:31:52.229: WARN/dalvikvm(10604): VFY: rejected Lgl;.a > (Landroid/content/Context;Ljava/lang/String;)Landroid/graphics/Bitmap; > 02-10 18:31:52.229: WARN/dalvikvm(10604): Verifier rejected class Lgl;
You have annoyed the verifier. What version of Android are you running on? Fixes for a bunch of things went into 2.0, though this doesn't look familiar. Opcode 0x0c is a move-result-object instruction. type=2 is a "conflict" type, meaning that the verifier couldn't conclusively determine what type of object lives in that register. This could be a problem with the Dalvik verifier, or with ProGuard taking too many liberties with moving data around. I'd need to see the .class file containing the "gl.a" method, and ideally have the whole .jar full of classes so I can run "dx" on it to generate the Dalvik instructions. If you'd like me to look at it, you can file a bug on b.android.com and attach the .jar, or just send it to me and reference this message. -- 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
