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#51723 - libx64 running into illegal instruction on LRMI_init call
Attached to Project:
Community Packages
Opened by Erika (rrika) - Sunday, 06 November 2016, 16:51 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 07 November 2016, 03:20 GMT
Opened by Erika (rrika) - Sunday, 06 November 2016, 16:51 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 07 November 2016, 03:20 GMT
|
DetailsIn libx86's backend for x86_64 (thunk.c) there is an intentional zero deref:
*((char *)0) = 0x4f; /* Make sure that we end up jumping back to a halt instruction */ Assuming this can't be right GCC inserts an undefined instruction after this. Compiler flags "-fno-delete-null-pointer-checks" disables this behavior. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Monday, 07 November 2016, 03:20 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#48120
Monday, 07 November 2016, 03:20 GMT
Reason for closing: Duplicate
Additional comments about closing:
FS#48120?I mean… from what I can tell every user of libx86 should crash