Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#42405 - [libffi] consider enabling EMUTRAMP compatibility feature
Attached to Project:
Arch Linux
Opened by Daniel Micay (thestinger) - Thursday, 16 October 2014, 14:25 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 26 October 2014, 11:00 GMT
Opened by Daniel Micay (thestinger) - Thursday, 16 October 2014, 14:25 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 26 October 2014, 11:00 GMT
|
Detailslibffi has support for making use of PaX's EMUTRAMP rather than injecting executable code at runtime. The feature is tiny so it would be nice to make it available by passing --enable-pax_emutramp to configure. In the past it lacked runtime detection, but now it checks /proc/self/status so there are no drawbacks to turning it on.
I think the previous lack of runtime detection is why there's a configure flag at all. The similar SELinux support is enabled by default. https://github.com/atgreen/libffi/blob/0403f332b1f478696c30d3d8a0e2f6eef24aaf88/src/closures.c#L175-L221 |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Sunday, 26 October 2014, 11:00 GMT
Reason for closing: Implemented
Additional comments about closing: libffi 3.1-3
Sunday, 26 October 2014, 11:00 GMT
Reason for closing: Implemented
Additional comments about closing: libffi 3.1-3