[Soot-list] Any parsing restriction

[Steven Arzt]

No, it's not. It actually works given that you have a proper JDK on your
classpath and that the Java exception classes are at least loadable to level
HIERARCHY. The complete story can be found in one of the issue reports on
Github. Short version: If we have an exception handler for two different
exception types, Soot needs to find a common supertype. This is however only
possible if we have a class hierarchy of the exception types.

We could theoretically add a hack that uses java.lang.Throwable in case we
don't have a hierarchy.

-----Ursprüngliche Nachricht-----
Von: soot-list-bounces at CS.McGill.CA [mailto:soot-list-bounces at CS.McGill.CA]
Im Auftrag von Marc-André Laverdière
Gesendet: Donnerstag, 24. Juli 2014 15:01
An: soot-list at CS.McGill.CA
Betreff: Re: [Soot-list] Any parsing restriction

Also, the Java 7 piped exception style is still unhandled. That's gonna get
fixed 'at some point', meaning 'whenever I'm done writing that paper' :)

Marc-André Laverdière-Papineau
Doctorant - PhD Candidate

On 07/24/2014 03:13 AM, Diptikalyan Saha wrote:
> Hi,
> 
> Is there any known restriction on which (like java8) byte-code class 
> files soot can parse and instrument.
> 
> Regards,
> Diptikalyan.
> 
> 
> 
> 
> _______________________________________________
> Soot-list mailing list
> Soot-list at CS.McGill.CA
> https://mailman.CS.McGill.CA/mailman/listinfo/soot-list
> 
_______________________________________________
Soot-list mailing list
Soot-list at CS.McGill.CA
https://mailman.CS.McGill.CA/mailman/listinfo/soot-list