commit 6c055d92f3cfac32cbbc16bfffc7369a8b77bd88
author meg-gupta <megupta@microsoft.com> Wed Jan 17 02:12:29 2018
committer meg-gupta <megupta@microsoft.com> Wed Jan 17 02:12:29 2018
tree 7276d06e0e6eb02ed10d686e5b5efc7415054296
parent 2fd420bdbe68f005feb6830e887b12bc214ab9f1
parent dee125d086d66a92641611b59eee504732a0df59

[MERGE #4535 @meg-gupta] Fix setting hasBailout when there are inlined functions in try/catch

Merge pull request #4535 from meg-gupta:fixCatchEatingUpEx

Fixes OS#15078638

When we bailout executing trycode from within OP_TryCatch, we complete the execution of the current function enclosing the try/catch in the interpreter.
If there was an exception within the try region, it is caught and handled accordingly in ProcessTryHandlerBailOut which reconstructs try/catch/finally frames
when we bailout midway executing code within OP_TryCatch. If there was an exception outside the try region, the catch of the OP_TryCatch ends up catching it,
because it happens to be on the callstack. For this we use the hasBailOut bit which is per function, so we know that this exception has to be passed above.

When we have inlined functions inside the try, and for bailouts inside the inlined code, we do not set the hasBailedOut bit, so that the enclosing functions catch in OP_TryCatch catches it.

But when we bailout from inlined code inside try, we execute inlined code, as well as the enclosing function's code in the interpreter.
We will be execution code past the try/catch of the current function in the interpreter. Now if any code outside the eh region throws,
we will catch that in OP_TryCatch which happens to be on the callstack. And we will end up handling it instead of passing above because we have not set the hasBailedOutBit from the bailout point.

This change fixes this issue. We pass a pointer to the hasBailedOutBit and set it once we have finished executing the inlined frames and are ready to process the interpreter frame of the current function.