[Soot-list] Soot Dacapo Issue

[Zhou, Tong]

Hi Eric,

Thanks for the reply! I was just wondering if Soot has a mode such that it only tries to resolve the classes on the command line and does not try to resolve classes referenced by these classes. Thanks!

-Tong
________________________________
From: Eric Bodden <eric.bodden at uni-paderborn.de>
Sent: Monday, February 4, 2019 3:48 AM
To: Zhou, Tong
Cc: soot-list at CS.McGill.CA
Subject: Re: [Soot-list] Soot Dacapo Issue

Hi Tong.

Can you be more specific? What’s the error you are seeing? And what’s the exact command line?

Eric

> On 2. Feb 2019, at 00:31, Zhou, Tong <tz at gatech.edu> wrote:
>
> Hi,
>
> I am trying to follow the tutorial from https://github.com/Sable/soot/wiki/Using-Soot-and-TamiFlex-to-analyze-DaCapo, but ran into an error.
>
> I first ran "java -javaagent:poa-x.y.z.jar -jar dacapo-9.12-MR1-bach.jar avrora" and that dumped some classes in "out/" (dumped classes). But when I tried to run Soot on these dumped classes, Soot had difficulty resolving classes that are not dumped but referenced by the dumped classes. I also tried "-allow-phantom-refs", and that couldn't fix it either. Both "out/" and dacapo.jar were in Soot's class path. Anyone know how to fix this? I just wanted to run Soot just on the argument classes, without having to resolve all referenced classes. Either suppressing this resolving or fixing it works for me. Thanks!
>
> -Tong
>
> _______________________________________________
> Soot-list mailing list
> Soot-list at CS.McGill.CA
> https://mailman.CS.McGill.CA/mailman/listinfo/soot-list

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