Mike McCormack <[EMAIL PROTECTED]> writes:
>> ---
>> err:virtual:map_image Image was mapped at 0x11c000: standard load address for a
>> Win32 program (0x0040) not available
>> err:virtual:map_image Do you have exec-shield or prelink active?
>> wine: could not load L"G:
Peter Riocreux wrote:
vars.pe_size = 0x0100;
vars.pe_address = (void*)0x0040;
// wld_reserve_wine_memory( pe_file, &vars.pe_address, &vars.pe_size );
mmap( vars.pe_address, vars.pe_size, PROT_NONE,
MAP_FIXED|MAP_PRIVATE|MAP_ANON, -1, 0);
Is this a get-it-working-
Peter Riocreux wrote:
It seems to be behaving as if none of your cunning
exec-shield-avoidance code is in there. The error messages certainly
seem to indicate this:
---
err:virtual:map_image Image was mapped at 0x11c000: standard load address for a Win32
program (0x00400
Mike McCormack <[EMAIL PROTECTED]> writes:
> What's the problem with wineconsole?
It seems to be behaving as if none of your cunning
exec-shield-avoidance code is in there. The error messages certainly
seem to indicate this:
---
err:virtual:map_image Image was mapped at 0
What's the problem with wineconsole?
I discovered a bug in the calculation of the area to reserve when
parsing the PE header, so I'll write a fix for that too.
Mike
Peter Riocreux wrote:
Have tested this a little and seems alright (a few offsets versus the
CVS as of 10:00 GMT, but applies clean
Have tested this a little and seems alright (a few offsets versus the
CVS as of 10:00 GMT, but applies cleanly). Alas our license for the
tool I was testing it with is not currently available, so I can't test
it out properly. It does at least load the first binary cleanly
though, so that is definit
Hi,
Here's a new patch for exec-shield.
Changes against the last patch:
* reserve only the area required by the PE EXE if launched from
CreateProcess (else just a default slab)
* pass the reserved area to wine, so wine knows about it
* unmap the preloader after it is no longer used
Again, co
