Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Valgrind Reports Useful?

0 views

Skip to first unread message

Chromatic

unread,

Feb 28, 2006, 5:13:26 PM2/28/06

to Perl 6 Internals

Hi there,

I just managed to get Valgrind working on my Linux PPC box. Are Valgrind
(memcheck, cachegrind, etc) reports useful from various platforms? If so, is
there a good example PIR file to run that stresses sufficient code (or should
someone add a new testgrind target that collects these reports)?

-- c

Will Coleda

unread,

Feb 28, 2006, 5:19:01 PM2/28/06

to chromatic, Perl 6 Internals

Running "make test" in languages/tcl should be pretty painful.

Chromatic

unread,

Feb 28, 2006, 5:42:21 PM2/28/06

to Will Coleda, Perl 6 Internals

On Tuesday 28 February 2006 14:19, Will Coleda wrote:

> Running "make test" in languages/tcl should be pretty painful.

Some tests will fail (STDERR is different), but you can set $ENV{VALGRIND} and
anything that uses Parrot::Test will run it. Nifty.

-- c

Leopold Toetsch

unread,

Mar 4, 2006, 11:47:33 AM3/4/06

to chromatic, Perl 6 Internals

Not useful ;) - eminently useful and very welcome. I've created a TODO
ticket about that some time ago. We should be able to test (at least) 2
things:

* memcheck: any access to uninitialized memory is a bug, double frees
and such of course too
* --leak-check: we should eventually get parrot leak free with
--destroy-at-end
(no chance to pass that currently)

>
> -- c

leo

0 new messages