Here''s a description of Purify''s behavior I dug up:
Extensive Runtime Error Detection
To catch errors throughout your application, Rational Purify for UNIX
uses Object Code Insertion (OCI) technology to intercept memory
accesses by inserting additional instructions into the object code
before every Load and Store operation. One major advantage to OCI is
completeness: all code, including third party and shared libraries,
is checked in this manner. Even hand optimised assembly code can be
checked. OCI helps Purify precisely locate more types of errors in
more areas of your application than any other similar tool. This
completeness assures you that bugs are detected even when they
manifest themselves only in vendors or third party libraries.
This Object Code Insertion sounds immensely like what Dtrace does,
only limited to memory accesses.
If you ran a dtrace script on something that was running with purify,
it might not explode, but I don''t
know that the Purify results would be accurate with dtrace changing
things around.
Did you ever try it to see what would happen?
ckl
p.s. libumem works just fine with Dtrace.
On Feb 14, 2006, at 10:15 AM, Gary Combs wrote:
>
>
> Will DTRACE interoperate with Purify?
>
> TIA,
> Gary
> --
> Gary Combs
> Product Architect
>
> Sun Microsystems, Inc.
> 3295 NW 211th Terrace
> Hillsboro, OR 97124 US
> Phone x32604/+1 503 715 3517
> Fax 503-715-3517
> Email Gary.Combs at Sun.COM
>
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org