Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Avoid assertion in case of stack overflow from stitched trace.
Reported by Sergey Bronnikov. Fixed by Sergey Kaplun. (cherry-picked from commit 1d75cd4) When we exit from a stitched trace due to the Lua stack overflow error, the Lua and JIT stacks are not synchronized, and they won't be as long as the mentioned error is raised. Because of that, we get the incorrect bytecode instruction in `debug_framepc`. This patch fixes this behavior, so the `debug_framepc` now returns `NO_BCPOS` for this case. Maxim Kokryashkin: * added the description and the test for the problem Part of tarantool/tarantool#9145
- Loading branch information