Wine & Valgrind 2.2.0

James Hawkins truiken at gmail.com
Fri Mar 11 09:39:39 CST 2005


On Fri, 11 Mar 2005 17:12:35 +0200 (EET), Saulius Krasuckas
<saulius2 at ar.fi.lt> wrote:
> On Wed, 9 Mar 2005, Robert Shearman wrote:
> > I notice there has been interest from developers wanting to run valgrind
> > with wine. I have been doing this successfully with the attached patch
> > applied.
> 
> That's very nice to hear, Rob.  Thanks. :-)
> 
> > Note that there are some false positives from the thread start routines
> > caused by a bug in valgrind. Apparantly this is fixed in the latest cvs,
> > but I have not tried it.
> 
> I have tried CVS version (several minutes old) of it, but I am not sure
> these false positives are gone.  You may look at the head of an attachment
> I am sending.
> 
> > I find the --tool=memcheck option the most useful, which can be used for
> > finding the source of memory corruption.
> 
> Fine, but can you help me to fight an error saying "SEGMENT MAPS NOT OK" ?
> I try running 'wine Diablo.exe' and get something like that:
> 
> | INV 2 FAILED: seg 0x1C490000-0x1C492000 crosses boundaries of mapping 0x1C490000-0x1C491000
> | INV 1 FAILED: seg -0x1C490000 does not end at mapping 0x1C492000-0x1C490000 end
> | INV 1 FAILED: mapping 0x1C491000-0x1C492000 (prot=rwx file=/usr/local/lib/wine/ole32.dll.so) is before 0x1C492000-0x1C498000
> |
> |
> | vvvvv SEGMENT MAPS NOT OK vvvvv
> | seg: 0x400000-0x401000 (r--)   19  mapping 0x400000-0x401000 r--  /mnt/antras/Diablo/Spawn/Diablo_s.exe
> | seg: 0x401000-0x470000 (r-x)    9  mapping 0x401000-0x470000 r-x
> | seg: 0x470000-0x47A000 (r--)    9  mapping 0x470000-0x47A000 r--
>   ...
> | seg: 0x1C440000-0x1C441000 (rw-)    9  mapping 0x1C440000-0x1C441000 rw-
> | seg: 0x1C441000-0x1C48F000 (r-x) 4219  mapping 0x1C441000-0x1C48F000 r-x  /usr/local/lib/wine/ole32.dll.so
> | seg: 0x1C48F000-0x1C490000 (rw-)   19  mapping 0x1C48F000-0x1C490000 rw-  /usr/local/lib/wine/ole32.dll.so
> | seg: 0x1C490000-0x1C492000 (rwx)   19  mapping 0x1C490000-0x1C491000 rwx  !!! /usr/local/lib/wine/ole32.dll.so
> | INV 2 FAILED: seg 0x1C490000-0x1C492000 crosses boundaries of mapping 0x1C490000-0x1C491000
> | INV 1 FAILED: seg -0x1C490000 does not end at mapping 0x1C492000-0x1C490000 end
> | INV 1 FAILED: mapping 0x1C491000-0x1C492000 (prot=rwx file=/usr/local/lib/wine/ole32.dll.so) is before 0x1C492000-0x1C498000
> | seg: 0x1C492000-0x1C498000 (rw-)   19  mapping 0x1C492000-0x1C498000 rw-  /usr/local/lib/wine/ole32.dll.so
>   ...
> | seg: 0xB5956000-0xB5A56000 (rwx) 2009  mapping 0xB5956000-0xB5A56000 rwx
> | seg: 0xBFFFE000-0xC0000000 (rwx) 2108  mapping 0xBFFFE000-0xC0000000 rwx
> | ^^^^^ SEGMENT MAPS NOT OK ^^^^^
> 
> And then valgrind terminates.  Where is the problem?  Something is wrong
> with the ole32.dll.so file?
> 
> Full output log goes attached.

Try running valgrind with wine-pthread or wine-kthread instead of
wine, because valgrind doesn't run child processes in it's vm.

-- 
James Hawkins



More information about the wine-devel mailing list