[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: "*toclose" vs. sandboxes / embedded environments
- From: Roberto Ierusalimschy <roberto@...>
- Date: Wed, 19 Dec 2018 10:46:20 -0200
> Roberto> I must say that this whole process of changing pcall/xcall
> Roberto> seems somewhat smelly.
>
> Maybe so, but the primary reason I took on the project at all was that
> the previous version had half a dozen unfixable crash bugs caused by
> playing fast and loose with the interaction between Lua and PG.
> Accordingly, in my version I have tried to be as strict as possible
> about the correctness of all interactions with the PG code.
>
> [...]
If I understood correctly, the problem is accesses to PG between
an error and its proper handling.
Wouldn't be enough some internal flag to disable all operations? An
error would set that flag, and some explicit operation (done after the
pcall, in case of errors) would reset it?
-- Roberto
- References:
- "*toclose" vs. sandboxes / embedded environments, Andrew Gierth
- Re: "*toclose" vs. sandboxes / embedded environments, Roberto Ierusalimschy
- Re: "*toclose" vs. sandboxes / embedded environments, Andrew Gierth
- Re: "*toclose" vs. sandboxes / embedded environments, Roberto Ierusalimschy
- Re: "*toclose" vs. sandboxes / embedded environments, Andrew Gierth
- Re: "*toclose" vs. sandboxes / embedded environments, Soni "They/Them" L.
- Re: "*toclose" vs. sandboxes / embedded environments, Patrick Donnelly
- Re: "*toclose" vs. sandboxes / embedded environments, Andrew Gierth
- Re: "*toclose" vs. sandboxes / embedded environments, Roberto Ierusalimschy
- Re: "*toclose" vs. sandboxes / embedded environments, Andrew Gierth