Skip to content

Failing instrumentation #2

@floyd-fuh

Description

@floyd-fuh

Hi there,

When instrumenting code with kelinci, I often get:

$ java -cp ../../instrumentor/build/libs/kelinci.jar edu.cmu.sv.kelinci.instrumentor.Instrumentor -i example.jar -o example-instrumented.jar
Instrumenting class: org/example/test/Parser.class
Exception in thread "main" java.lang.RuntimeException: java.lang.ClassNotFoundException: com.otherexample.other.SomeClassname
        at org.objectweb.asm.ClassWriter.getCommonSuperClass(Unknown Source)
        at org.objectweb.asm.ClassWriter.a(Unknown Source)
        at org.objectweb.asm.Frame.a(Unknown Source)
        at org.objectweb.asm.Frame.a(Unknown Source)
        at org.objectweb.asm.MethodWriter.visitMaxs(Unknown Source)
        at org.objectweb.asm.MethodVisitor.visitMaxs(Unknown Source)
        at org.objectweb.asm.ClassReader.a(Unknown Source)
        at org.objectweb.asm.ClassReader.b(Unknown Source)
        at org.objectweb.asm.ClassReader.accept(Unknown Source)
        at org.objectweb.asm.ClassReader.accept(Unknown Source)
        at edu.cmu.sv.kelinci.instrumentor.Instrumentor.main(Instrumentor.java:63)

For now I just make sure it will use the non-instrumented classes when it fails in my fork (see floyd-fuh@32f405e), however, I think that's not the best option. Any idea why it could fail? Are there any dependencies that could be missing during instrumentation or anything like that?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions