[Soot-list] Exception management with Soot

Paolo Giannoccaro pgiannoccaro at yahoo.com
Sun Mar 25 12:33:50 EDT 2018


 Thank you Jan,I will try to work on PackManager class (on local first, if results are good I will create a pull request).
Paolo
    On Sunday, 25 March 2018, 12:51:42 CEST, Jan Peter Stotz <jan-peter.stotz at sit.fraunhofer.de> wrote:  
 
 Hi Paolo,

now I understand. There is an Exception caught by Soot and you only see 
it in the logs/console output. From my perspective there is only one way 
to deal with this problem:

Modify the source code of Soot so that the Exception is correctly 
handled. You can modify it and create a Github pull request.

 From my perspective the problem is located in soot.PackManager [1].
It uses multiple times ThreadPoolExecutor and executes Runnable within 
those Executors. The disadvantage of Runnables is that the Exceptions 
are lost if not handled separately.
Instead Callable<Void> implementations should be used. When submitting a 
Callable you get a Future. When checking the future for the result (via 
get()) a potential Exception thrown inside of the Callable is propagated 
to the outside.

This is what you need.

Jan

[1] 
https://github.com/Sable/soot/blob/develop/src/main/java/soot/PackManager.java
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20180325/164b36ad/attachment.html>


More information about the Soot-list mailing list