Re: [Valgrind-users] Release plan for Valgrind 3.0

[Julian S. <ju...@va...>]

>  - From basic tests, it appears to me that it is quite a bit slower (2.4
> SVN starts up the server in 11 seconds, whereas 3.0 SVN takes 23
> seconds).

The new JIT is a lot slower than the 2.4 one, unfortunately.  Most of the
startup delay is likely to be translation time.


> - Interestingly, 2.4 doesn't report _any_ of these uninitialised values,
> and when running under 3.0 the server segfaults whereas it doesn't under
> 2.4 or without valgrind.

Euh, that sucks.  Do you get any useful logging output just before the
crash?

Does it still crash with --tool=none?

What about with --tool=none --vex-iropt-level=0 ?


>
> I am wondering if 3.0 and 2.4 report different cpu capabilities (such as
> mmx, sse etc) 

Quite possibly.  Rerun with -v -v and look for a line like this:

--5075-- Host CPU: arch = X86, subarch = x86-sse2

J