Repo Added
|
Files
89
|
Badge
README BADGES
|
push
github
Avoid out-of-range PC for stack overflow error from snapshot restore. Reported by Sergey Kaplun. (cherry picked from commit cd4af8ad8) When restoring a snapshot because of exiting by the check of the stack, the snapshot from the parent trace is used. For the correct error message, the snapshot map uses the next bytecode after the stored one. In case, when the PC in the snapshot is BC_RET* (the last bytecode in the prototype), there is no next value to be referenced, so this approach leads to the assertion failure in `lj_debug_framepc()`. This patch prevents this behaviour by checking the original bytecode and avoiding PC adjusting in the case of the last bytecode in the prototype. Sergey Kaplun: * added the description and the test for the problem Part of tarantool/tarantool#11278
5713 of 6046 branches covered (94.49%)
Branch coverage included in aggregate %.
4 of 4 new or added lines in 3 files covered. (100.0%)
1 existing line in 1 file now uncovered.21798 of 23508 relevant lines covered (92.73%)
3856730.0 hits per line
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|
Builds | Branch | Commit | Type | Ran | Committer | Via | Coverage |
---|---|---|---|---|---|---|---|
15604081467 | skaplun/lj-1359-bad-pc-on-snap-restore-stackov | Avoid out-of-range PC for stack overflow error from snapshot restore. Reported by Sergey Kaplun. (cherry picked from commit cd4af8ad8) When restoring a snapshot because of exiting by the check of the stack, the sn... | push | github |
93.09 |