DragonFly kernel List (threaded) for 2004-07
Re: wine running?
-----BEGIN PGP SIGNED MESSAGE-----
On Tuesday 13 July 2004 08:18, Yury Tarasievich wrote:
> Is there any possibility of getting wine running?
> Current wine-on-df build can't do "mmap of entire memory space" in
> ntdll.dll.so, which is what not-so-current-(but post-20040615)-wine does
> on freebsd-4, I believe. Ktrace shows lots of failed attempts to do mmap
> with first arg incrementing up to 0xffff...something
Check the archives of wine-devel. There was a rather lengthy discussion of
this problem and what may be required to fix it. Perhaps the DFly team would
be amenable to the changes. :)
Quoting a message from John Birrel on this thread:
>At run time, the error:
>"wine: failed to initialize: /something/lib/wine/ntdll.dll.so: mmap of
>entire address space failed: Cannot allocate memory"
>is caused by Wine attempting to mmap memory outside the user process
>address space. I see mmap addr around 0xd8100000 (mostly 0xd81eccd8)
>whereas the user address space limit on FreeBSD current is 0xbfc00000
>(at least on my system).
>This failure is well before any thread library issues are encountered.
>I ran a test of mmap on FreeBSD current to see what address space I
>was able to mmap. Using objdump to identify the pages that the test
>program was linked to load in, the test program was able to mmap MAP_ANON,
>MAP_FIXED, MAP_NOCORE all memory from 0x0 to 0xbfc00000, except the
>pages at which the test program was mapped at.
>I'll look further into how Wine is mmap'ing memory on FreeBSD.
It was determined that wine should not be changed at that it would likely be
better to change FreeBSD's mmap address allocation algorithm. The thread is
called "Wine on FreeBSD current".
AIX and Storage Administrator
UT MD Anderson Cancer Center
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
-----END PGP SIGNATURE-----