Ran
|
Jobs
1
|
Files
89
|
Run time
9s
|
Badge
Embed ▾
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, we cannot determine the bytecode position properly, and 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
5397 of 5995 branches covered (0.0%)
Branch coverage included in aggregate %.
20669 of 23358 relevant lines covered (88.49%)
2762988.79 hits per line
Lines | Coverage | ∆ | File |
---|---|---|---|
1 |
93.09 |
-0.33% | src/lj_ir.c |
2 |
75.38 |
0.0% | src/lj_crecord.c |
5 |
95.03 |
-0.89% | src/lj_opt_mem.c |
5 |
85.78 |
-2.16% | src/lj_sysprof.c |
6 |
94.74 |
-4.31% | src/lj_str.c |
9 |
90.15 |
-1.64% | src/lj_ffrecord.c |
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 7287728345.1 | 89 |
88.8 |
GitHub Action Run |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|