Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Bronnikov <sergeyb@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit] Fix predict_next() in parser (for real now).
Date: Fri, 10 Jan 2025 14:10:19 +0300	[thread overview]
Message-ID: <Z4EAGw2sAggMI2Gi@root> (raw)
In-Reply-To: <847b75f4-07a9-4c99-83b1-d9833197a82d@tarantool.org>

Hi, Sergey!
Thanks for the review.

On 10.01.25, Sergey Bronnikov wrote:
> Hi, Sergey,
> 
> thanks for the patch!
> 
> test is passed with reverted patch.
> 
> With original reproducer luajit segfaults.
> 
> CMake options:  cmake -S . -B build -DCMAKE_BUILD_TYPE=Debug 
> -DLUA_USE_APICHECK=ON -DLUA_USE_ASSERT=ON

You must run this test with Valgrind enabled to see the failure as it is
mentioned in the commit. The original reproducer is clumsy and unstable
-- any slight change of the parser may break it. This reproducer is much
simpler, robust, and more readable.

> 
> 
> Sergey
> 
> On 09.01.2025 18:01, Sergey Kaplun wrote:

<snipped>

> > +-- The parsing of the `for` iterator uses the incorrect check for
> > +-- `fs->bclim`, which allows the usage of an uninitialized value,
> > +-- so the test fails under Valgrind.

<snipped>

-- 
Best regards,
Sergey Kaplun

  reply	other threads:[~2025-01-10 11:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 15:01 Sergey Kaplun via Tarantool-patches
2025-01-10 11:06 ` Sergey Bronnikov via Tarantool-patches
2025-01-10 11:10   ` Sergey Kaplun via Tarantool-patches [this message]
2025-01-13 14:29     ` Sergey Bronnikov via Tarantool-patches
2025-01-13 15:18 ` Sergey Bronnikov via Tarantool-patches
2025-01-13 15:25   ` Sergey Kaplun 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=Z4EAGw2sAggMI2Gi@root \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=sergeyb@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH luajit] Fix predict_next() in parser (for real now).' \
    /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