[Bug 5407] New: wine-preloader receives SIGKILL on start on machines with >1GiB RAM

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=5407

Summary: wine-preloader receives SIGKILL on start on machines
                    with >1GiB RAM
           Product: Wine
           Version: 0.9.11.
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: blocker
          Priority: P2
         Component: wine-binary
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

This bug is related to bug 2574 ( http://bugs.winehq.org/show_bug.cgi?id=2574 ).

What Mike McCormack points out, seems to be correct. According to "objdump -f
/usr/bin/wine-preloader", the start address of "wine-preloader" is 0x7c000000.
However, when using a Linux kernel which is configured to "2G/2G user/kernel
split" (as explained here: http://kerneltrap.org/node/6067 ), the kernel address
space already starts at 0x78000000 (not at 0x80000000), making it impossible to
map wine-preloader to the user virtual memory from start address 0x7c000000 on
(because the user virtual memory ends at 0x78000000) .

Thus, "wine-preloader" immediately receives a KILL signal from the kernel.

This bug should be fixed. It makes wine unable for wine-users who have a
properly configured kernel and more than 1GiB RAM (but not more than 2GiB RAM).
This user group should enable "2G/2G user/kernel split" for optimal performance
if they do run applications which need more than 2GB virtual address space. I
doubt that wine needs so much virtual address space in every instance.

As a solution, for example, "wine-preloader" could use a slightly lower start
address like 0x74000000.