Mikhail Fursov wrote: > It proves that we have a bug here that can be fixed without lazy > resolution fixes. The only problem is to minimize the testcase.
Let me know if I can be of any further help -- but it sounds like we need someone who understands the JITed stack walker, or other likely candidates for this bug. Running the snippet code in a simple test case passes ok for me, but it may not have been jitted. What is the command-line option to force full optimized jitting eagerly? Regards, Tim
