[prev in list] [next in list] [prev in thread] [next in thread]
List: soot-list
Subject: Re: [Soot-list] Bug when -oaat is used with -outjar
From: "Bodden, Eric" <eric.bodden () sit ! fraunhofer ! de>
Date: 2013-04-19 9:41:31
Message-ID: 58876E53-2CD4-42E4-BE51-495A7CFEAF96 () sit ! fraunhofer ! de
[Download RAW message or body]
Thanks. I fixed this.
Eric
On 14.04.2013, at 05:25, Saswat Anand <saswat78@gmail.com> wrote:
>
> When -oaat and -outjar are used together, the output jar file remains empty.
>
> That is because, even with -oaat flag, PackManager:writeOutput is called from \
> soot.Main at line 199. I dont think there is no need for that call because with \
> -oaat flag, the classes have already been output at that point.
> The fix is to move that call to writeOutput from Soot.Main to inside the else \
> branch in PackManager.runPacks() method.
> Saswat
>
>
> _______________________________________________
> Soot-list mailing list
> Soot-list@sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
--
Eric Bodden, Ph.D., http://sse.ec-spride.de/ http://bodden.de/
Head of Secure Software Engineering Group at EC SPRIDE
Tel: +49 6151 16-75422 Fax: +49 6151 16-72051
Room 3.2.14, Mornewegstr. 30, 64293 Darmstadt
_______________________________________________
Soot-list mailing list
Soot-list@sable.mcgill.ca
http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic