Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Kaplun <skaplun@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit] Rework stack overflow handling.
Date: Fri, 6 Jun 2025 16:42:30 +0300	[thread overview]
Message-ID: <a6b51143-48f9-4b0c-9709-06761f68083e@tarantool.org> (raw)
In-Reply-To: <aELv1x5f0QmStptE@root>

[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]

Hello,

LGTM with a comment below.

Sergey

On 6/6/25 16:40, Sergey Kaplun wrote:

<snipped>

>>> diff --git a/test/LuaJIT-tests/lang/stackov.lua b/test/LuaJIT-tests/lang/stackov.lua
>>> index 8afa86b4..b052ad80 100644
>>> --- a/test/LuaJIT-tests/lang/stackov.lua
>>> +++ b/test/LuaJIT-tests/lang/stackov.lua
>> I don't get why we need this change. With reverted patch this test is
>> passed.
> With reverted -- yes. But after reworking the stack overflow handling,
> it is possible that there is no place on the stack to call the error
> handler (in that case, `debug.traceback`). Since this thing looks like
> implementation-defined behaviour, I prefer to make the test less strict.
>
Please add a message to the test or/and to the commit message.
>>> @@ -31,13 +31,17 @@ end
>>>    do --- Base test.
>>>      local err, s = xpcall(f, debug.traceback)
>>>      assert(err == false)
>>> -  test_error_msg(f, s)
>>> +  -- There is no place on the stack to invoke the handler.
>>> +  -- Just test the error reason.
>>> +  assert(string.match(s, "stack overflow"))
>>>    end
>>>    
>>>    do --- Stack overflow with non-empty arg list.
>>>      local err, s = xpcall(g, debug.traceback, 1)
>>>      assert(err == false)
>>> -  test_error_msg(g, s)
>>> +  -- There is no place on the stack to invoke the handler.
>>> +  -- Just test the error reason.
>>> +  assert(string.match(s, "stack overflow"))
>>>    end
>>>    
>>>    do --- Vararg tail call with non-empty arg list. +slow
> <snipped>
>

[-- Attachment #2: Type: text/html, Size: 2346 bytes --]

  reply	other threads:[~2025-06-06 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25 13:42 Sergey Kaplun via Tarantool-patches
2025-06-06 12:54 ` Sergey Bronnikov via Tarantool-patches
2025-06-06 13:40   ` Sergey Kaplun via Tarantool-patches
2025-06-06 13:42     ` Sergey Bronnikov via Tarantool-patches [this message]
2025-06-06 13:48       ` Sergey Kaplun via Tarantool-patches
2025-06-06 16:22         ` Sergey Bronnikov via Tarantool-patches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a6b51143-48f9-4b0c-9709-06761f68083e@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=sergeyb@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH luajit] Rework stack overflow handling.' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox