[Soot-list] Using Soot for code coverage

[Arzt, Steven]

Hi Thibault,

The Soot plugin for Eclipse is heavily outdated and I don’t know anyone who is actively maintaining it at the moment. If you’re feeling lucky, you can try it, but I won’t make any promises about it.

Concerning your instrumentation question: Yes, Soot is able to instrument code. However, I don’t really understand your question. Soot translates all bytecode instructions (assuming you start from Java bytecode) into Jimple statements. You can then arbitrarily modify these jimple statements and delete existing ones or add new ones using transformers. Afterwards, Soot writes the new code back out into bytecode.

What do you mean by lines vs. statements?

Best regards,
  Steven

From: Soot-list [mailto:soot-list-bounces at cs.mcgill.ca] On Behalf Of Thibault Beziers la fosse
Sent: Friday, March 3, 2017 11:48 AM
To: soot-list at cs.mcgill.ca
Subject: [Soot-list] Using Soot for code coverage

Hello,
I've a question about Soot, it may have already been asked before, but I can't access to the Soot-list archives.

I'm currently building my own code coverage tool, I tried first using the ASM library, but the coverage is not precise enough (Line level).

I'd like to know if Soot is able to instrument the statements, and not only the lines (as ASM does).

Also I've some issues using Soot on Eclipse, more specifically the Soot eclipse plugin. I'm using Eclipse Modeling Neon 2, and the installation fails every time. (I followed the instructions on GitHub thought).

Thank you for your attention,
Best regards,

--
Thibault Béziers la Fosse

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20170303/032af723/attachment.html>