From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Kaplun <skaplun@tarantool.org> Cc: Sergey Bronnikov <estetus@gmail.com>, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit 2/2][v2] FFI: Turn FFI finalizer table into a proper GC root. Date: Thu, 15 Aug 2024 10:34:03 +0300 [thread overview] Message-ID: <3a3f7758-026b-437b-951b-4cc2ed4f2d2d@tarantool.org> (raw) In-Reply-To: <ZroLWtT4v2v5izWS@root> [-- Attachment #1: Type: text/plain, Size: 947 bytes --] Hello, Sergey, On 12.08.2024 16:17, Sergey Kaplun wrote: <snipped> >> >>> Also, please add here comment about `sizeof(buff) - 1` too. > Please add a comment that the terminating '\0' is considered by parser > as part of the input, so we must chomp it. Updated: --- a/test/tarantool-c-tests/lj-1168-unmarked-finalizer-tab.test.c +++ b/test/tarantool-c-tests/lj-1168-unmarked-finalizer-tab.test.c @@ -89,6 +89,10 @@ unmarked_finalizer_tab_gcmark(void *test_state) /* Not trigger GC during `lua_openffi()`. */ lua_gc(L, LUA_GCSTOP, 0); + /* + * The terminating '\0' is considered by parser as part of + * the input, so we must chomp it. + */ int res = luaL_loadbufferx(L, buff, sizeof(buff) - 1, "test_chunk", "t"); if (res != LUA_OK) { > > <snipped> > [-- Attachment #2: Type: text/html, Size: 2182 bytes --]
next prev parent reply other threads:[~2024-08-15 7:34 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-09 10:45 [Tarantool-patches] [PATCH luajit 0/2][v2] Fix cdata finalizer table Sergey Bronnikov via Tarantool-patches 2024-07-09 10:45 ` [Tarantool-patches] [PATCH luajit 1/2][v2] FFI: Treat cdata finalizer table as a GC root Sergey Bronnikov via Tarantool-patches 2024-07-09 11:52 ` Sergey Kaplun via Tarantool-patches 2024-07-09 15:43 ` Sergey Bronnikov via Tarantool-patches 2024-07-10 13:13 ` Sergey Kaplun via Tarantool-patches 2024-07-23 18:18 ` Sergey Bronnikov via Tarantool-patches 2024-08-12 13:32 ` Sergey Kaplun via Tarantool-patches 2024-08-15 7:32 ` Sergey Bronnikov via Tarantool-patches 2024-08-15 8:33 ` Sergey Kaplun via Tarantool-patches 2024-07-09 10:45 ` [Tarantool-patches] [PATCH luajit 2/2][v2] FFI: Turn FFI finalizer table into a proper " Sergey Bronnikov via Tarantool-patches 2024-07-09 12:14 ` Sergey Kaplun via Tarantool-patches 2024-07-10 11:39 ` Sergey Bronnikov via Tarantool-patches 2024-07-10 14:08 ` Sergey Kaplun via Tarantool-patches 2024-07-23 18:29 ` Sergey Bronnikov via Tarantool-patches 2024-08-12 13:17 ` Sergey Kaplun via Tarantool-patches 2024-08-15 7:34 ` Sergey Bronnikov via Tarantool-patches [this message] 2024-08-15 8:34 ` Sergey Kaplun via Tarantool-patches 2024-07-09 11:54 ` [Tarantool-patches] [PATCH luajit 0/2][v2] Fix cdata finalizer table Sergey Kaplun via Tarantool-patches 2024-07-10 11:41 ` Sergey Bronnikov via Tarantool-patches 2024-08-15 8:15 Sergey Bronnikov via Tarantool-patches 2024-08-15 8:21 ` [Tarantool-patches] [PATCH luajit 2/2][v2] FFI: Turn FFI finalizer table into a proper GC root Sergey Bronnikov via Tarantool-patches 2024-08-15 9:38 ` Maxim Kokryashkin 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=3a3f7758-026b-437b-951b-4cc2ed4f2d2d@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=estetus@gmail.com \ --cc=sergeyb@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 2/2][v2] FFI: Turn FFI finalizer table into a proper GC root.' \ /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