When spawning a new container (via clone()) we allocate stack for
lxcContainerChild(). So far, we allocate 4 pages for the stack
and this used to be enough until we started rewriting everything
to glib. With glib we switched to g_strerror() which localizes
errno strings and thus increases stack usa
On Fri, Aug 04, 2023 at 03:38:07PM +0200, Michal Privoznik wrote:
> When spawning a new container (via clone()) we allocate stack for
> lxcContainerChild(). So far, we allocate 4 pages for the stack
> and this used to be enough until we started rewriting everything
> to glib. With glib we switched
When spawning a new container (via clone()) we allocate stack for
lxcContainerChild(). So far, we allocate 4 pages for the stack
and this used to be enough until we started rewriting everything
to glib. With glib we switched to g_strerror() which localizes
errno strings and thus increases stack usa
On 8/3/23 22:54, Olaf Hering wrote:
> Thu, 3 Aug 2023 21:38:02 +0200 Michal Prívozník :
>
>> it looks like we're using { 0 } everywhere else so that's why I went with it.
>
> I was under the impression {} is valid. But apparently it is not,
> so I learned something new today: "ISO C forbids empty