[Sablevm-developer] using a Soot-transformed classpath
Brought to you by:
egagnon
From: Chris P. <chr...@ma...> - 2004-03-06 03:29:23
|
Hi, I want to make SableVM use Soot-transformed versions of the non-native portion of Classpath. I have the output from Soot in the application directory where I try to run SableVM, but the classes aren't getting loaded even with '-c .' specified as an option. What is the best way to do this? For an application that transforms just gnu.* and java.* I tried: cd ~/lib/sablevm/classpath mv gnu gnu-old mv java java-old ln -s ~/path-to-sootOutput/java ln -s ~/path-to-sootOutput/gnu but that didn't work (cannot create vm). Also, on a related note -- does anyone know of a good way to catch those classes which are only referenced from native code and thus not found by Soot? (I'm assuming such classes exist for certain applications). Profiling SableVM for the application and then comparing against the Soot output for whole-program-including-classpath-transformation seems like the only realistic choice, but maybe I'm missing something (it's not difficult to do, but it's not a real analysis). Cheers, Chris |