RE: Method not found although apparently exists

["Eric Bodden" <eric@bodden.de>]

Hello.

> If I were debugging this, I would start by putting some println's just
> before the exception to tell you what methods Soot thinks the 
> class has.
Ok, will probably try to have look at this next week. But as it is
working for you I assume that there should be some strange installation
on the sun cluster I am working with. But actually this error should not
occur anyway, that's for sure...

> I believe CHA should work in the presence of phantom classes. 
> But then, I didn't write CHA, and I haven't seen your exceptions, so 
> you know more about it than I do.

I think we already had that: Whenever I have phantom classes and apply
CHA, I get a Type Error(12):

soot.jimple.toolkits.typing.TypeException: Type Error(12)
        at
soot.jimple.toolkits.typing.TypeVariable.error(TypeVariable.java:532)
        at soot.jimple.toolkits.typing.TypeNode.lca(TypeNode.java:329)
        at
soot.jimple.toolkits.typing.TypeVariable.fixApprox(TypeVariable.java:654
)
        at
soot.jimple.toolkits.typing.TypeVariable.computeApprox(TypeVariable.java
:553)
        at
soot.jimple.toolkits.typing.TypeResolver.compute_approximate_types(TypeR
esolver.java:878)
        at
soot.jimple.toolkits.typing.TypeResolver.compute_array_depth(TypeResolve
r.java:360)
        at
soot.jimple.toolkits.typing.TypeResolver.resolve_step_2(TypeResolver.jav
a:290)
        at
soot.jimple.toolkits.typing.TypeResolver.resolve(TypeResolver.java:194)
        at
soot.jimple.toolkits.typing.TypeAssigner.internalTransform(TypeAssigner.
java:59)
        at soot.BodyTransformer.transform(BodyTransformer.java:58)
        at soot.BodyTransformer.transform(BodyTransformer.java:80)
        at soot.jimple.JimpleBody.applyPhaseOptions(JimpleBody.java:118)
        at
soot.coffi.CoffiMethodSource.getBody(CoffiMethodSource.java:111)
        at soot.SootMethod.getBodyFromMethodSource(SootMethod.java:89)
        at soot.SootMethod.retrieveActiveBody(SootMethod.java:311)
        at
soot.jimple.toolkits.invoke.ClassHierarchyAnalysis.newInvokeGraph(ClassH
ierarchyAnalysis.java:77)
        at
soot.jimple.toolkits.invoke.ClassHierarchyAnalysis.newInvokeGraph(ClassH
ierarchyAnalysis.java:43)

You wrote:
"I believe Type Error(12) occurs when for some type used in your
program,
not all of its superclasses are available. They are required in order
for Soot to be able to computer declared types to local variables."

So there does not really seem to be a solution for that, am I right?
Could the person who wrote the CHA probably tell me something about
that?

Thanks again,
Eric