As in the Chromium binary included with a specific distro, or is it a problem with the Chromium build system? Chromium seems like one of the projects that should have this sort of thing figured out.
-
-
-
Binary was built by the user reporting the problem (this awful linker output is not being handled right by musl - we skip mapping its bss) so I think it's the Chromium build system (probably an evil linker script) doing it.
-
My guess would be they're doing some awful hack and have code to mprotect most of it R-X and RW- later.
-
I'm looking forward to the day that I can run one of Gentoo's hardened musl profiles on my main desktop without tearing my hair out over stuff like this. Maybe I should just go for it and send patches to musl and/or broken 3rd party projects.
-
In this case it's a real musl bug that kept it from working, but a Chromium bug that they're (apparently) trying to do this since it consumes an extra 160MB of commit charge.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.