Everest (MonoMod) cannot run on glibc 2.41 due to executable stack restrictions

[ndren]

My mods and Everest install are up to date

Yes

I have recreated the bug with only Everest OR a minimum number of mods enabled

Yes

Describe the bug

Hey, I'm running into issue MonoMod/MonoMod#198 on Everest: 5285-azure-6656e. With the glibc update MonoMod is no longer able to use an executable stack.

Updating MonoMod should fix the issue, see MonoMod/MonoMod#212.

Unfortunately, that patch seems to only be in Git (unreleased), so I'm not sure what the best course of action is. It seems it has been version bumped as part of that, so should be ok.

Steps to reproduce

1. Try running Celeste through Everest.
2. See as the game crashes.

Expected behavior

The game should run correctly.

Operating System

Arch Linux

Everest Version

5285-azure-6656e

Mods required to reproduce

N/A

Additional context

See attached log.

As a tip to anyone having the same issue in the base game, try execstack -c for each library in the lib64 folder (https://aur.archlinux.org/packages/execstack), since that fixed base Celeste for me but not Everest runtime.

log.txt

[Popax21]

You can work around this issue for now by executing execstack -s <path to the Celeste binary>. That being said, it will take a while (2 to 3+ weeks) for a MonoMod version bump to trickle down into stable, especially since the jump will be non-insignificant for Everest.

[SnipUndercover]

There is an ongoing PR which aims to update MM (#827). I believe there was a reluctance to doing so because of jbevain/cecil#953 breaking the T type constraint on UserIO.Save<T>, but reading the issue it seems that a workaround was found.
Though, by looking at #827, it seems that mods don't really like this, and I'm not sure whether the mentioned bug issue was ever fixed.

We have also had this issue reported over on the Celeste Discord Server (see here).