You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, there are other places in src/lj_err.c where the same issue is possible -- lj_err_optype and lj_err_optype_call at least, and maybe I've missed some others. So, it comes to mind that a better fix would possibly be a more general frame fix up, so we won't encounter this kind of issue again.
The text was updated successfully, but these errors were encountered:
MikePall
changed the title
[Linux/x86] Segmentation fault during on-trace exception handling
Segmentation fault during on-trace exception handling
Aug 13, 2023
Thanks to Maxim Kokryashkin. LuaJIT#1034
(cherry-picked from commit d5bbf9c)
This patch fixes the same issue with frame, as the previous
one, but now for the table overflow error in the `err_msgv`
function. The test for the problem uses the table of GC
finalizers, although they are not required to reproduce the
issue. They only used to make the test as simple as possible.
Resolvestarantool/tarantool#562Resolvestarantool/tarantool#8652
Part of tarantool/tarantool#8825
Thanks to Maxim Kokryashkin. LuaJIT#1034
(cherry-picked from commit d5bbf9c)
This patch fixes the same issue with frame, as the previous
one, but now for the table overflow error in the `err_msgv`
function. The test for the problem uses the table of GC
finalizers, although they are not required to reproduce the
issue. They only used to make the test as simple as possible.
Resolvestarantool/tarantool#562
Part of tarantool/tarantool#8825
On the LuaJIT 2.1 branch (8635cba at the moment), if one makes a build like this:
And then runs the following script:
It results in a successfully handled
pcall
for the first case, and a segmentation fault for the second case:Backtrace:
The issue seems to be the same as in #1004 -- a frame fix is required, but now for
err_msgv
. Proposed fix:After its application the result is correct:
However, there are other places in
src/lj_err.c
where the same issue is possible --lj_err_optype
andlj_err_optype_call
at least, and maybe I've missed some others. So, it comes to mind that a better fix would possibly be a more general frame fix up, so we won't encounter this kind of issue again.The text was updated successfully, but these errors were encountered: