[oilpan] Fix stack limit check for recursive tracing
The limit was defined as ~0ul (unsigned long) which is unsigned 32bit on Windows 64bit and thus extended with 0 for uintptr_t. This results in bogus return of StackFrameDepth::IsSafeToRecurse of true even though recursion might be disabled due to stack pressure. Bug: chromium:798479 Change-Id: I13710b3dca4d3785e35aedd8ba5f7ece167b20e4 Reviewed-on: https://chromium-review.googlesource.com/847580 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#526666}
Showing
Please register or sign in to comment