Re: Source File again

[Ondrej Lhotak <olhotak@sable.mcgill.ca>]

I think the place where this should go is soot.coffi.Util, in the method
resolveFromClassFile. This is called from resolveClassAndSupportClasses
in soot.SootResolver.

The whole class file loading from coffi thing has never been entirely
clear to me, so I could be wrong.

Should something similar be done when resolving from Jimple files? And
the upcoming Java-to-Jimple? I think the place where all three of these
meet is in resolveClassAndSupportClasses in soot.SootResolver.

I guess we should have a keep-source-file option, along the lines of
keep-line-number and keep-bytecode-offset.

Ondrej

On Wed, Aug 20, 2003 at 10:38:26PM -0400, Chen Fu wrote:
> There have been some disscussion about source file tag  on this list while
> no clear conclusion.  Has some one implemented this?
> 
> 
> I think the right place to put the tag is SootClass instead of method or
> unit.  I tried to find the place to the code so i focused on the loading of
> a class. It seems to me reading of class attributes is done in
> 
> soot.coffi.ClassFile.loadClassFile(InputStream). the attributes are then put
> into some public attributes of ClassFile
> 
> But I can't put the code into that method because I have no access to
> SootClass there.  And I found there are several call sites of the above
> function in soot.coffi.Util located in different methods.
> 
> Could you tell me which one is on the critical path of loading a class?
> 
> Thanks
>