Tarantool development patches archive
 help / color / mirror / Atom feed
From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Maxim Kokryashkin <max.kokryashkin@gmail.com>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit 0/2] Fix frames for on trace errors
Date: Wed, 27 Sep 2023 12:33:28 +0000	[thread overview]
Message-ID: <ZRQhGBFg5iCsxHNL@tarantool.org> (raw)
In-Reply-To: <cover.1693910172.git.m.kokryashkin@tarantool.org>

Max,

I've checked the patchset into tarantool/master branch in
tarantool/luajit and bumped a new version in master.

On 05.09.23, Maxim Kokryashkin via Tarantool-patches wrote:
> This patchset fixes frames for OOM and TABOV on-trace errors.
> Tests are disabled on macOS because of macOS 12 issues with
> old version of libunwind.
> 
> PR: https://github.com/tarantool/tarantool/pull/8909
> Branch: https://github.com/tarantool/luajit/tree/fckxorg/lj-1004-oom-error-frame
> Issues:
> https://github.com/luajit/luajit/issues/1004
> https://github.com/luajit/luajit/issues/1034
> 
> Maxim Kokryashkin (1):
>   Fix frame for on-trace out-of-memory error.
> 
> Mike Pall (1):
>   Fix frame for more types of on-trace error messages.
> 
>  src/lj_err.c                                  |  8 +++++
>  test/tarantool-tests/CMakeLists.txt           |  1 +
>  .../lj-1004-oom-error-frame.test.lua          | 36 +++++++++++++++++++
>  .../lj-1004-oom-error-frame/CMakeLists.txt    |  1 +
>  .../lj-1004-oom-error-frame/testoomframe.c    | 17 +++++++++
>  .../lj-1034-tabov-error-frame.test.lua        | 27 ++++++++++++++
>  6 files changed, 90 insertions(+)
>  create mode 100644 test/tarantool-tests/lj-1004-oom-error-frame.test.lua
>  create mode 100644 test/tarantool-tests/lj-1004-oom-error-frame/CMakeLists.txt
>  create mode 100644 test/tarantool-tests/lj-1004-oom-error-frame/testoomframe.c
>  create mode 100644 test/tarantool-tests/lj-1034-tabov-error-frame.test.lua
> 
> --
> 2.41.0
> 

-- 
Best regards,
IM

      parent reply	other threads:[~2023-09-27 12:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05 10:39 Maxim Kokryashkin via Tarantool-patches
2023-09-05 10:39 ` [Tarantool-patches] [PATCH luajit 1/2] Fix frame for on-trace out-of-memory error Maxim Kokryashkin via Tarantool-patches
2023-09-07  8:07   ` Sergey Bronnikov via Tarantool-patches
2023-09-08 13:18     ` Maxim Kokryashkin via Tarantool-patches
2023-09-12  9:53       ` Sergey Bronnikov via Tarantool-patches
2023-09-11  8:04   ` Sergey Kaplun via Tarantool-patches
2023-09-11 11:52     ` Maxim Kokryashkin via Tarantool-patches
2023-09-05 10:39 ` [Tarantool-patches] [PATCH luajit 2/2] Fix frame for more types of on-trace error messages Maxim Kokryashkin via Tarantool-patches
2023-09-07  8:11   ` Sergey Bronnikov via Tarantool-patches
2023-09-07  8:56     ` Maxim Kokryashkin via Tarantool-patches
2023-09-07 10:06       ` Sergey Bronnikov via Tarantool-patches
2023-09-11  8:20   ` Sergey Kaplun via Tarantool-patches
2023-09-11 13:45     ` Maxim Kokryashkin via Tarantool-patches
2023-09-27 12:33 ` Igor Munkin via Tarantool-patches [this message]

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=ZRQhGBFg5iCsxHNL@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=imun@tarantool.org \
    --cc=max.kokryashkin@gmail.com \
    --subject='Re: [Tarantool-patches] [PATCH luajit 0/2] Fix frames for on trace errors' \
    /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