The PurifyPlus solution adds performance profiling and code coverage analysis capabilities. PurifyPlus is a runtime analysis tool suite that monitors your program as it runs and reports on key aspects of its behavior: How much memory does it use?
Does it leak memory? Does it contain memory access errors? How long does it take to run; where are the bottlenecks? How much of the source code is actually running? These key analysis features are all separate from the core "correctness" question: "Does it work? The major components of PurifyPlus are: Purify for memory usage tracking and memory error detection Quantify for performance analysis, code flow, and thread visualization PureCoverage for source code coverage analysis.
Continuous Integration. Request a Meeting. Contributors , references and license information then follows. Pre-requisites and dependencies are listed in following and minimal versions required are tested against Travis CI meaning that they come natively with OSX and the Ubuntu Trusty release. These are also the default ones fetched by CMake an internet connection is required for this. Once the mandatory dependencies are present, git clone from the GitHub repository :.
The main purify executable lives either in the build directory or in the in the bin subdirectory of the installation directory. Additionally, a config file with the settings used will be saved and time-stamped, helping for reproducibility and book-keeping.
If you want to use Docker instead, you can build an image using the Dockerfile available in the repository or pulling it from DockerHub. To run the container and mount the directory is with:. There you can run purify as shown above.
Check the contributors page github. If you use PURIFY for work that results in publication, please reference the webpage and our related academic papers:. It is possible to tell CMake exactly which libraries to compile and link against.
0コメント