[Soot-list] Bytecode level transformer

[Marc-André Laverdière-Papineau]

Isn't that an output option?

You can have the following round trip

.class -> jimple -> analyses -> .class

And there are other output options:
http://www.sable.mcgill.ca/soot/tutorial/intro/


Marc-André Laverdière-Papineau
Doctorant - PhD Candidate

On 26/06/13 09:26 PM, Al wrote:
> You could convert jimple to baf (java bytecode).
> 
> Al
> 
> On Jun 26, 2013, at 7:39 PM, Marc-André Laverdière-Papineau <marc-andre.laverdiere-papineau at polymtl.ca> wrote:
> 
>> Hello,
>>
>> Soot normally works at a higher level representation, called Jimple,
>> which is somewhere between Java and the bytecode.
>>
>> There is a representation called Coffi that you can use to deal with the
>> bytecode, but I don't think that a lot of the analyses will work on coffi.
>>
>> But my question is why you would like to work on the bytecode in the
>> first place?
>>
>> Marc-André Laverdière-Papineau
>> Doctorant - PhD Candidate
>>
>> On 26/06/13 05:47 PM, Ivan Postolski wrote:
>>> Hello Soot List, newbie question:
>>>
>>>    I'm currently coding a body transformer on soot and want to know how
>>> get the bytecode instructions that read a value from the heap, like
>>> aaload or getfield, and then do some transforming after those. Is this
>>> possible with soot and Jimple? 
>>>
>>> I also want to get into the invokes and the bytecode them point to. like
>>> "iterator.next()"
>>>
>>> Thanks
>>>
>>> Ivan.-
>>>
>>>
>>> _______________________________________________
>>> Soot-list mailing list
>>> Soot-list at sable.mcgill.ca
>>> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>> _______________________________________________
>> Soot-list mailing list
>> Soot-list at sable.mcgill.ca
>> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>