Re: java.lang.NullPointerException in Hierarchy

[redhat <redhat@xlnt-software.com>]

Thanks Ondrej,

Ondrej Lhotak <olhotak@sable.mcgill.ca> wrote:

> To find classes, Soot looks in paths in the --soot-classpath option to
> Soot, not the -cp option to java.

	I understood that, I just wondered why the java.path System.property
wouldn't contain it, so it can be read.

> If you get any "Phantom class" warnings, then it is normal for the
> typing system to not work. Make the classes available to get rid of the
> warnings first.
> > one I see occuring is `Aborting: can't find classfilejava.awt.LayoutManager'
> > The only way I've been able to stop that is by adding the class in the
> > `--soot-classpath prj/',	it is ignored when placed in `-cp prj/'

	I actually meant that it wasn't reading it from rt.jar, so I needed to
put it in the project directory. I found the message in the bug track
that related to this, unzipping rt.jar ans jsse.jar, and this I may have
spotted where this occures for me.

Transforming <classname>... java.util.ConcurrentModificationException
	at soot.util.HashChain$LinkIterator.hasNext(HashChain.java:465)
	at soot.Main.handleClass(Main.java:2134)
	at soot.Main.processClasses(Main.java:1724)
	at soot.Main.run(Main.java:1623)
	at java.lang.Thread.run(Thread.java:536)

	I've noticed this happens mainly when I extend classes from
javax.swing.*. Even though classes that I extend from those have no
problem, AFAIK.

tnx,

blaze your trail
--
redhat

'I am become Shiva, destroyer of worlds'