[Soot-list] unreachable code in jimple files?

[Martin Schäf]

No, but it's the other way around. Of course, everything can throw a
throwable, but finally blocks apparently catch arbitrary objects ... a
friend pointed me to this article:
http://stackoverflow.com/questions/5749898/what-can-you-throw-in-java
So apparently, the bytecode makes a difference between throwable and any.


On Wed, Sep 3, 2014 at 1:28 AM, Bodden, Eric <eric.bodden at sit.fraunhofer.de>
wrote:

> Hi Martin.
>
> > I have a new opinion and this might also be interesting for another
> email thread that talks about detecting finally blocks:
> > In
> > >             21   135   170   Class java/lang/Throwable
> > >             21   135   179   any
> > Is it possible that the "catch" is the first line, and the finally the
> the second? Because, as finally is executed anyway, it actually does also
> catch stuff that is not "Throwable" (even though you have to switch off the
> bytecode verifier for that).
>
> Well, every thing you can throw in Java is, by definition, a Throwable
> (hence the name). Thus Throwable is really the same as any.
>
> It might well be that javac compiles finally-blocks with "any" but that's
> then just an artifact of the computation. Any other compiler could just as
> well use "Throwable".
>
> > On the other hand, how would you pitch a problem like this to the JDK
> folks / how do you reach them?
>
> I think this here would be the appropriate list:
> http://mail.openjdk.java.net/mailman/listinfo/compiler-dev
>
> Cheers,
> Eric
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20140903/7f860a31/attachment.html