Related articles |
---|
how does purify work? toddhoff@my-deja.com (2000-08-04) |
Re: how does purify work? pfaffben@msu.edu (Ben Pfaff) (2000-08-05) |
Re: how does purify work? cfc@world.std.com (Chris F Clark) (2000-08-05) |
Re: how does purify work? plakal@cs.wisc.edu (2000-08-05) |
Re: how does purify work? Martin.Raabe@WindRiver.com (Martin Raabe) (2000-08-05) |
Re: how does purify work? nsrcccw@leonis.nus.edu.sg (2000-08-05) |
Re: how does purify work? ralph@inputplus.demon.co.uk (2000-08-10) |
Re: how does purify work? gvmt@bgl.vsnl.net.in (Venkatesha Murthy G.) (2000-08-10) |
[1 later articles] |
From: | Ben Pfaff <pfaffben@msu.edu> |
Newsgroups: | comp.os.vxworks,comp.compilers,comp.programming |
Date: | 5 Aug 2000 20:39:49 -0400 |
Organization: | Michigan State University |
References: | 00-08-027 |
Keywords: | tools, storage |
toddhoff@my-deja.com writes:
> If one wanted to build a Purify like tool, does anyone know how it
> would be done? I don't really understand what it does and haven't
> found much related info.
Have a look at GNU Checker, available from
ftp://alpha.gnu.org/gnu
or *much* newer snapshots via CVS at cvs.gnu.org. It doesn't
work in the same way as Purify, as I understand it, but it does
the same job. Older versions of Checker worked by using a
modified version of the GNU assembler that inserted calls to
check every memory reference; newer versions of Checker work by
using a modified version of the GNU C compiler that does the same
thing.
(FWIW, I am co-maintainer of Checker, but not the author.)
Return to the
comp.compilers page.
Search the
comp.compilers archives again.