Re: [Sablevm-developer] using a Soot-transformed classpath

[Chris P. <chr...@ma...>]

Grzegorz B. Prokopski wrote:

>W liście z sob, 06-03-2004, godz. 21:41, Etienne Gagnon pisze: 
>  
>
>>On Fri, Mar 05, 2004 at 11:45:07PM -0500, Chris Pickett wrote:
>>    
>>
>>>>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.
>>>>        
>>>>
>>How about compiling a version of SableVM with
>>--enable-debugging-features and then launching sablevm like this:
>>
>> sablevm -v --property sablevm.verbose.methods=true ...
>>
>>This should show you the complete sequence of called methods.  I guess
>>we should really document these boot-time properties somewhere.  Any
>>volunteer?
>>    
>>
>
>Ehrm...! does _anybody_ read manual pages?! ;-)
>
>$ man sablevm
>
>(though suggestions/improvements are welcomed)
>  
>

not sure if you last changed it very recently, but for me, only 
sablevm.verbose.methods and sablevm.verbose.instructions are there.  
perhaps the best solution is to generate that portion of the file from 
vm_args.(m4?).c -- that way, it always stays up to date.

cheers,
chris

p.s.  java.lang.Object superclass problem is solved for me, but soot and 
d-java are still broken, for those who aren't on the soot list.