Wine & Valgrind 2.2.0
saulius2 at ar.fi.lt
Fri Mar 11 09:40:25 CST 2005
On Fri, 11 Mar 2005, James Hawkins wrote:
> 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 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
> > And then valgrind terminates. Where is the problem? Something is wrong
> > with the ole32.dll.so file?
> Try running valgrind with wine-pthread or wine-kthread instead of
> wine, because valgrind doesn't run child processes in it's vm.
Yes, I already am running that way (wine-pthread). W/o wine-pthread name
or w/o --trace-children=yes option supplied I capture nothing usefull.
And BTW, wine under valgrind runs slowly now. AFAICS, a lot more slowly
than the stable v2.2.0.
More information about the wine-devel