Re: WWDC / XCode v2.0?
Re: WWDC / XCode v2.0?
- Subject: Re: WWDC / XCode v2.0?
- From: Tobias Sargeant <email@hidden>
- Date: Sun, 4 Jul 2004 08:57:55 +1000
Message: 3
Date: Fri, 02 Jul 2004 07:51:39 +0100
Subject: Re: WWDC / XCode v2.0?
From: Chris Ridd <email@hidden>
To: <email@hidden>
If you're just talking about the Linux/x86 version of purify, I'd
agree.
However the Solaris version works quite differently - on Linux purify
parses
each source file (and inserts instrumentation, I guess) before
compiling it,
and on Solaris you purify when linking.
Pre-instrumenting covers both these cases. Purify produces an executable
containing code to check memory accesses, etc. Valgrind takes a
different
approach (virtualising the CPU), which you can read about here:
http://developer.kde.org/~sewardj/docs-2.0.0/mc_techdocs.html
Valgrind's a nice tool. It isn't always better than purify, but it is
nice
to be able to choose between multiple tools :-)
I've had both Valgrind and Purify fail on me, but in my opinion the
sheer simplicity of being able to run an executable under valgrind
without
any need to preprocess the executable or source code makes it a more
effective debugging tool. I'm more likely to use it periodically in a
preemptive fashion, and when I need it to find a problem it integrates
nicely with gdb and doesn't get in my way. All of which are hallmarks
of a good (debugging) tool.
As someone who doesn't make money directly from programming, however, I
, in any case, would much prefer a port of Valgrind to a port of Purify,
simply because I'll never be able to afford Purify. I've worked in a
number of IT jobs where I had access to Purify or Boundschecker (when
they worked), and that was great, but Bioinformtics research relies,
almost competely, on Open Source.
Toby.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.