Unfortunately, we took a look at this again and the fix is obviously wrong: some arguments are pushed on the stack by privateSnippetExecutor but never removed; this is almost certain to lead to incorrect behaviour.
It looks like unwind support is needed for this after all.
Unfortunately, we took a look at this again and the fix is obviously wrong: some arguments are pushed on the stack by privateSnippetE xecutor but never removed; this is almost certain to lead to incorrect behaviour.
It looks like unwind support is needed for this after all.