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
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

In 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 
Comment by Doug Newgard (Scimmia) - Sunday, 06 November 2016, 17:04 GMT
Is this the same as  FS#48120 ?
Comment by Erika (rrika) - Monday, 07 November 2016, 03:05 GMT
I don't know how to properly load the coredump in the linked report but it would make sense.
I mean… from what I can tell every user of libx86 should crash
Comment by Doug Newgard (Scimmia) - Monday, 07 November 2016, 03:20 GMT
Alright, we'll continue there, then. If it turns out to be different, request this be reopened.

Loading...