Ran
|
Jobs
1
|
Files
89
|
Run time
3s
|
Badge
Embed ▾
README BADGES
|
push
github
Fix snapshot PC when linking to BC_JLOOP that was a BC_RET*. Reported by Arseny Vakhrushev. Fix contributed by Peter Cawley. (cherry-picked from commit 5c46f4773) As specified in the comment in `lj_record_stop`, all loops must set `J->pc` to the next instruction. However, the chunk of logic in `lj_trace_exit` expects it to be set to `BC_JLOOP` itself if it used to be a `BC_RET`. This wrong pc results in the execution of random data that goes after `BC_JLOOP` in the case of restoration from the snapshot. This patch fixes that behavior by adapting the loop recording logic to this specific case. NOTICE: This patch is only a part of the original commit, and the other part is backported in the previous commit. The patch was split into two, so the test case becomes easier to implement since it can now depend on this assertion instead of memory layout. Maxim Kokryashkin: * added the description and the test for the problem Part of tarantool/tarantool#9145
5341 of 5973 branches covered (0.0%)
Branch coverage included in aggregate %.
5 of 5 new or added lines in 1 file covered. (100.0%)
20455 of 23294 relevant lines covered (87.81%)
2751565.52 hits per line
Lines | Coverage | ∆ | File |
---|---|---|---|
1 |
95.92 |
-0.08% | src/lj_asm.c |
1 |
99.04 |
1.44% | src/lj_str.c |
2 |
91.11 |
-0.32% | src/lj_alloc.c |
3 |
95.7 |
0.0% | src/lj_record.c |
4 |
75.77 |
-0.32% | src/lj_opt_fold.c |
15 |
89.3 |
0.22% | src/lj_err.c |
42 |
64.44 |
-20.44% | src/lj_sysprof.c |
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 6406081177.1 | 89 |
88.14 |
GitHub Action Run |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|