On 05/21/18 12:23 AM, benta...@chez.com wrote:
Hi I used to compile Wine and it used to work quite well but recent
update to OpenIndiana nailed it quite hard as it seg fault's for
anything more than --version.
Segmentation Fault (core dumped)
Update date | illumos v. | result
2018-03-28 | 243bebc0df | ok
2018-05-06 | 4ff15898b7 | ko
2018-05-18 | 8dfe5547fb | ko
$ dbx /opt/wine/bin/wine core
core file header read successfully
program terminated by signal SEGV (no mapping at the fault address)
0xfeda8ee8: wine_ldt_init_fs+0x0049: movw %eax,%fs
$ mdb /opt/wine/bin/wine core
Loading modules: [ libc.so.1 ld.so.1 ]
08046aa8 libwine.so.1.0`wine_ldt_init_fs+0x49(1007, 8046ad0, 8046ae8,
08046ae8 ntdll.dll.so`signal_init_thread+0xb8(3fff8000, 0, 8046b58,
08046b58 ntdll.dll.so`thread_init+0x33d(8063de8, 0, 7ff5680c, feda964a,
08046b88 ntdll.dll.so`__wine_process_init+0x17(3, 8063de8, 8063e04, a,
08046bb8 libwine.so.1.0`wine_init+0x135(2, 8047054, 8046bdc, 400)
08046fe8 main+0x112(8046fec, fed5f2c8, 8047028, 8051168, 2, 8047054)
08047028 _start_crt+0x97(2, 8047054, fefd1c00, 0, 0, 0)
08047048 _start+0x1a(2, 8047188, 804719b, 0, 80471a7, 8047aa9)
Rebuilding wine with the new "environment" doesn't change the outcome.
I was wondering if it was related to the KPTI code but starting with
KPTI disable doesn't change things.
So I come to see if anyone has an idea how to approach this as I don't
know how to interpret the debuggers output.
Hi. The issue seems similar to sbcl one. I'd blame KPTI, but this need
confirming. Can you check it on illumos-gate prior to KPTI changes?
system administrator of Southern Federal University IT department
openindiana-discuss mailing list