On 2023/05/13 17:06:50 +0200, Sebastien Marie wrote:
> Hi,
>
> Currently, when sbcl starts, the console shows a "map stack for pid XXX
> failed"
> message.
>
> After searching a bit, sbcl is badly using sigaltstack(2) by using a
> MAP_STACK
> memory with RWX protection. The syscall fails wit
Hi,
Currently, when sbcl starts, the console shows a "map stack for pid XXX failed"
message.
After searching a bit, sbcl is badly using sigaltstack(2) by using a MAP_STACK
memory with RWX protection. The syscall fails with EINVAL (and a printf(9)
message is shown).
By reducing the protection
