In message <[EMAIL PROTECTED]>
Julian Seward <[EMAIL PROTECTED]> wrote:
>> So the wine folks do much the same as we do - wine-preloader is run,
>> which is a static executable linked to load at a high address. That
>> then mmaps everything from 0 up to 1.5Gb before acting as an ELF
>> loader and loading the real wine executable and it's shared libraries
>> into memory and transferring control.
>
> What happens if you change V's load address to say 0x90000000
> (by messing with valt_load_address_normal in configure.in) ?
I did actually try that but it didn't help much as valgrind stuck
a block of SkAnonV memory below 0x60000000 which still stopped wine's
preloader reserving that memory :-(
Tom
--
Tom Hughes ([EMAIL PROTECTED])
http://www.compton.nu/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Valgrind-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
