I think I've gotten further with this #FreeBSD #wine issue, knowledge-wise. The program I run for it does some live patching in memory (basically reads in a .dll and binary patches it in memory)
This all runs just fine in #Linux but fails in FreeBSD.
The system call I could find for it in WINE debugging was: KERNEL32.ReadProcessMemory
I also get this dreaded message:
wineserver: file_set_error() can't map error: Cannot allocate memory
This is FreeBSD 14.3, wine-devel 10.12.
Have tried disabling ASLR, enabling W^X (which I know is bad), have tried both 64-bit and 32-bit (WINEARCH=win32) prefixes. Same problem happens.
Is FreeBSD preventing WINE programs from reading each others' memory? I don't even know if it even got to the write part, it couldn't read it at all.
Please boost far and wide and many thanks in advance to anyone in the FreeBSD gaming community who might know the answer here (or a friendly FreeBSD dev?)
#introduction time...
Hey I'm Tom. Long-time Sysadmin. Came to BSD from Linux in 2005, been a happy BSD user since. I still have to use Linux in my every day work, but I am looking at ways of putting more BSD into use if possible.
I maintain a modest 6 OpenBSD ports (mostly games!)
When I'm not playing around with computers, I like playing my tenor and alto saxophones.