[Soot-list] Does soot preserve java bytecode offset information?

Arzt, Steven steven.arzt at sit.fraunhofer.de
Mon Feb 11 04:01:21 EST 2019


Hi Shuyang,

You can try to look into Unit.getTags(). If there is a BytecodeOffsetTag,
that's what you're looking for.

Best regards,
  Steven

-----Original Message-----
From: Soot-list <soot-list-bounces at cs.mcgill.ca> On Behalf Of Shuyang Liu
Sent: Friday, February 8, 2019 9:50 PM
To: soot-list at cs.mcgill.ca
Subject: [Soot-list] Does soot preserve java bytecode offset information?

Hello!

Recently my research requires me to find more detailed information on call
graphs of java programs. More specifically, in addition to knowing which
methods calls which methods (as shown by the call graph provided by soot), I
would like to know the java bytecode offset of each call site so that I can
distinguish some of the edges in the call graph. It seems to me that soot
does all of its analysis after translates java bytecode to its IR jimple and
it is not one to one mapping to the original java bytecode instructions. So
I wonder if soot preserve any java bytecode offset information at all? If
so, how can I access them? I was not able to find anything looking at the
soot source code but I could miss something.  

Thank you,
Shuyang Liu
_______________________________________________
Soot-list mailing list
Soot-list at CS.McGill.CA
https://mailman.CS.McGill.CA/mailman/listinfo/soot-list
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 9148 bytes
Desc: not available
URL: <https://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20190211/779d9bb9/attachment.p7s>


More information about the Soot-list mailing list