|
Ran
|
Jobs
1
|
Files
89
|
Run time
16s
|
Badge
README BADGES
|
push
github
Avoid assertion in case of stack overflow from stitched trace. Reported by Sergey Bronnikov. Fixed by Sergey Kaplun. (cherry-picked from commit 1d75cd4d7) 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
5377 of 5988 branches covered (0.0%)
Branch coverage included in aggregate %.
20629 of 23358 relevant lines covered (88.32%)
2749305.5 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 7207362079.1 | 0 |
88.62 |
GitHub Action Run |