 | IBM Rational Purify for Windows| Feature | Description | Benefit |
|---|
| Memory corruption and leak detection | Automatically pinpoints hard-to-find bugs |  Improved execution reliability |
|---|
| Unique instrumentation techniques | Instruments code at the byte or object level | No recompilation or re-linking is needed to analyze your code
Supports analysis of third party libraries |
|---|
| Server-side Java support | Install PurifyPlus on your Web server to analyze Java Server Pages (JSP) and Java servlets | Improve reliability and performance of server code as well as client applications |
|---|
| Runs directly inside leading IDEs, as well as stand-alone | Purify installs and operates directly within Visual Studio .NET, and Visual Studio .NET 2003 | No switching back and forth between different tools with different user interfaces
Provides for a more cohesive, more productive development experience
Test and analyze your code as it is being created
Extends your development experience with these IDEs to include runtime analysis
Stand-alone operation offers flexibility in how to perform runtime analysis |
|---|
| Comprehensive programming language support | Supports Java, C/C++, Microsoft's managed languages (VB.NET and C#) as well as the unmanaged languages (Visual C/C++) | Purify provides the only memory leak and corruption analysis tool you will need for all your Windows-based application development |
|---|
| Selective instrumentation | Allows you to select which modules of an application to analyze | Analyze only the modules you want without having to instrument the whole application
Choose only the components for which you are responsible
Provides greater flexibility for creating the test environment
Makes the data collection part of runtime analysis much easier |
|---|
IBM Rational Purify for Linux and UNIX| Feature | Description | Benefit |
|---|
| Memory corruption and leak detection | Automatically pinpoints hard-to-find bugs | Improved execution reliability |
|---|
| Unique instrumentation techniques | Instruments code at the byte or object level
| No recompilation or re-linking is needed to analyze your code
Supports analysis of third party libraries |
|---|
| Selective instrumentation | Allows you to select which modules of an application to analyze | Analyze only the modules you want without having to instrument the whole application
Choose only the components for which you are responsible
Provides greater flexibility for creating the test environment
Makes the data collection part of runtime analysis much easier |
|---|
 | |
|
