On Apr 16, 12:26 am, Tomasz Stechly <tomasz.stec...@gmail.com> wrote:
> When I am running the activity I am getting now different error. Do
> you know what it may be (see log below). Should I send separate
> message to the group?
The first bunch:
> D/installd( 27): DexInv: --- BEGIN '/data/app/vmdl67263.tmp' ---
> I/dalvikvm( 402): DexOpt: illegal method access (call
> Ljunit/framework/Assert;.failNotEquals
> (Ljava/lang/String;Ljava/lang/Object;Ljava/lang/Object;)V from
> Lgroovy/util/GroovyTestCase;)
> D/dalvikvm( 402): VFY: unable to resolve exceptionIdx=1153
> D/dalvikvm( 402): DexOpt: load 2026ms, verify 9272ms, opt 287ms
> D/installd( 27): DexInv: --- END '/data/app/vmdl67263.tmp' (success) ---
aren't fatal at this stage, but the classes in question will
eventually fail verification. I think you lost a chunk of the log
here; the actual message about the exception looks like "VFY: unable
to resolve exception class %u (%s)". Since these are just warnings at
this point, it's no big deal.
> I/ActivityManager( 66): Start proc com.stechly.hello for activity
> com.stechly.hello/.Hello: pid=409 uid=10020 gids={}
> W/dalvikvm( 409): VFY: unable to resolve direct method 15358:
> Ljava/lang/Object;.clone ()Ljava/lang/Object;
> W/dalvikvm( 409): VFY: rejecting opcode 0x70 at 0x0000
> W/dalvikvm( 409): VFY: rejected
> Lcom/stechly/hello/Hello;.super$1$clone ()Ljava/lang/Object;
> W/dalvikvm( 409): Verifier rejected class Lcom/stechly/hello/Hello;
This is... strange. Dalvik has "virtual" methods and "direct"
methods, the former being object instance methods, the latter
encompassing constructors and methods declared "static" or "private".
Object.clone() is a virtual method, but com.stechly.hello.Hello.super
$1$clone is attempting to invoke it as if it were a direct method.
The verifier is rejecting it.
I believe the correct VM behavior here is actually to resolve the
method and then throw an IncompatibleClassChangeError. Either way
your code isn't going to run.
I don't know if this is a bug in dx (using the wrong form of invoke-*)
or something weird in the class file. As with the initial problem,
sending samples to danfuzz should improve our diagnostic
abilities. :-)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
