valgrind-developers

[Valgrind-developers] 1.1.0 is out

[Julian S. <js...@ac...>]

Hi.  I just put 1.1.0 at http://developer.kde.org/~sewardj along with 
a long description thereof.  You might want to look at it.

Fixed various small probs stopping it from working right across multiple
distros (VMware is a tremendous help in testing).

> Julian:
>   - --run-libc-freeres option

done

>   - docs:
>       - read skin docs
>       - split up core/memcheck docs
>       - for addrcheck
>   - factor out addrcheck/memcheck commonality?

not done


> Me or Julian:
>   - docs:
>       - index describing each skin, basic overview.
>       - document skin_name:supp_name stuff

not done

> Me:
>   - Allow memcheck,addrcheck:Cond style multi-skin suppressions?

Interestingly, this was the only thing that really bit.  Some of the
memcheck suppression also apply to addrcheck, and not having them 
makes the addrcheck thing spew out a lot of garbage.  Any chance you
can push this along?

------

Vague plan (vague because now I don't know when I will have time to
get back to this):

- fix up all the above
- implement logging to a network socket 
- make it work on R H 8

and after that I'd like to freeze and stabilise for 1.2.0.  Dunno
exactly when we should start the 1_2_0 branch.

J

Re: [Valgrind-developers] 1.1.0 is out

[Nicholas N. <nj...@ca...>]

On Sun, 6 Oct 2002, Julian Seward wrote:

> Hi.  I just put 1.1.0 at http://developer.kde.org/~sewardj along with
> a long description thereof.  You might want to look at it.

One minor thing -- Cachegrind is called Cachegrind everywhere now, not
Cachesim.

> > Me:
> >   - Allow memcheck,addrcheck:Cond style multi-skin suppressions?
>
> Interestingly, this was the only thing that really bit.  Some of the
> memcheck suppression also apply to addrcheck, and not having them
> makes the addrcheck thing spew out a lot of garbage.  Any chance you
> can push this along?

Sure, how should I proceed -- ok to hack on HEAD?

N