[Soot-list] Current state of invokedynamic support in soot

[David Diepenbrock]

Dan,

>From my experience the latest 3.3.0 release has several commits that improve soot's ability to process lambdas.  If you're on an older release give upgrading a try.  I can tell you that 3.3.0 vs. 3.1.0 I see functionality that otherwise was broken after processing now works as expected.

Here's some of the changes in 3.3.0 that I tracked down when I was working soot processing with lambdas recently:
https://github.com/Sable/soot/pull/1078
https://github.com/Sable/soot/pull/1090

If you're already on 3.3.0 or newer then I'll have to punt.

Best,
David
________________________________
From: Soot-list <soot-list-bounces at CS.McGill.CA> on behalf of Daniel Peebles <pumpkingod at gmail.com>
Sent: Wednesday, June 12, 2019 9:28 AM
To: soot-list at cs.mcgill.ca
Subject: [Soot-list] Current state of invokedynamic support in soot

Hi all,

I’m running soot on a jar and it’s barfing with an error saying “Failed to convert” on a method that returns a java.util.function.Function from a lambda expression. The bytecode involves invokedynamic and I’m wondering if soot has trouble on that sort of code, and if so, what a good approach to dealing with it is.

Unfortunately I can’t share the code in question but might be able to reduce it later if it helps or if this behavior is unexpected.

Thanks,
Dan
_______________________________________________
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/20190612/bd4d31cd/attachment.html>