- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are there any tools, similar to Purify, to help locate memory leaks in C code on Linux on IA64? I believe that Purify for Linux is only available for the x86 architecture.
Link Copied
5 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
See "MemorySscape" by TotalView Technologies http://www.totalviewtech.com/support/ms-v-linux-ia64.html
--mark
--mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I also use Valgrind and highly recommend it.
Another commercial product for this problem is Insure++ from Parasoft.
http://www.parasoft.com/jsp/products/home.jsp?product=Insure&itemId=63
It has a nice interface, good diagnostics, its own compiler, but is very slow (like 50 times slower than normal debug run).
So is only good for pinpointing a known problem, not for generic testing (unless you do unit testing). Actually, valgrind is the same in this respect.
Insure also does static code analysis.
I have used Insure about 5 years ago, but it does not seem to evolve very much in the recent years.
On the other side Valgrind made great progress. Unfortunately, I still can't get what I liked most about Insure - a gui interface which will position me in the source line of the error, when a memory leak, or illegal memory access occurs.
Another commercial product for this problem is Insure++ from Parasoft.
http://www.parasoft.com/jsp/products/home.jsp?product=Insure&itemId=63
It has a nice interface, good diagnostics, its own compiler, but is very slow (like 50 times slower than normal debug run).
So is only good for pinpointing a known problem, not for generic testing (unless you do unit testing). Actually, valgrind is the same in this respect.
Insure also does static code analysis.
I have used Insure about 5 years ago, but it does not seem to evolve very much in the recent years.
On the other side Valgrind made great progress. Unfortunately, I still can't get what I liked most about Insure - a gui interface which will position me in the source line of the error, when a memory leak, or illegal memory access occurs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - dpeterc
I also use Valgrind and highly recommend it.
Another commercial product for this problem is Insure++ from Parasoft.
http://www.parasoft.com/jsp/products/home.jsp?product=Insure&itemId=63
It has a nice interface, good diagnostics, its own compiler, but is very slow (like 50 times slower than normal debug run).
So is only good for pinpointing a known problem, not for generic testing (unless you do unit testing). Actually, valgrind is the same in this respect.
Insure also does static code analysis.
I have used Insure about 5 years ago, but it does not seem to evolve very much in the recent years.
On the other side Valgrind made great progress. Unfortunately, I still can't get what I liked most about Insure - a gui interface which will position me in the source line of the error, when a memory leak, or illegal memory access occurs.
Another commercial product for this problem is Insure++ from Parasoft.
http://www.parasoft.com/jsp/products/home.jsp?product=Insure&itemId=63
It has a nice interface, good diagnostics, its own compiler, but is very slow (like 50 times slower than normal debug run).
So is only good for pinpointing a known problem, not for generic testing (unless you do unit testing). Actually, valgrind is the same in this respect.
Insure also does static code analysis.
I have used Insure about 5 years ago, but it does not seem to evolve very much in the recent years.
On the other side Valgrind made great progress. Unfortunately, I still can't get what I liked most about Insure - a gui interface which will position me in the source line of the error, when a memory leak, or illegal memory access occurs.
Valgrind is very good tool for profiling applicatin and finding memory leaks and runtime errors on Linux system
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - newtonesque
Are there any tools, similar to Purify, to help locate memory leaks in C code on Linux on IA64? I believe that Purify for Linux is only available for the x86 architecture.
Hi, I work at Intel ASDC (Argentina Software Development Center), we are developing an application in C++ and we are trying to use a runtime analysis tool to measure code coverage and find memory leaks. Our objective is compile the product that we are developing with ICC.
We made some tests with IBM Purify Plus compiling in debug mode as this tool requires. This tool does not work compiling with ICC but it works compiling with gcc or visual studio compiler.
Are you aware of this issue? Is there a known solution?
Thanks
Best Regards
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page