We think software tools should concentrate on one job at a time. Your memory leak tool should be all about memory issues – it shouldn’t also be trying to be a performance profiler and a deadlock detector at the same time.
It’s the difference between a set of chef’s knives and a swiss army knife.
The right tool for each job.
If you develop for Windows and use Visual Studio, C++ Builder, Delphi, QtCreator, MingW we have tools to help you. They can help you to find and fix bugs in C, C++, Delphi, Fortran, Visual Basic, C# and VB.Net.
We’ve helped thousands of software developers find, fix, and prevent bugs.
For 21 years we’ve been providing tools to tackle the biggest problems out there: our happy customers include giants like Adobe, Cisco, Intel, UBS, and HP.
Developer Suite includes software tools for the following tasks:
QA Suite includes software tools for the following tasks
Support Suite includes software tools for the following tasks:
I’m not getting much time these days to offer as much feedback as I would like, but I’m making good use of Memory Validator and Coverage Validator. These two tools have become a staple in my toolbox. Still looking forward to a new Thread Validator, nobody else (that I know of) can do a good job of this.
Thanks, this version works fine. Reran my big coverage run and it took 8.6 hours to run, very impressive considering it takes Rational Coverage 30 hrs. to do the same thing.
The source code is ~800,000 lines. I am running ~150 runs of the test driver with different input specifications.
I just installed and used Lua Coverage Validator for the first time. LCV is very impressive. I’ll be sending feedback as I use this. I did not try the tutorial, and that’s on my to-do list. Great product from what I touched on the first time. It identified one whole area of code missed by the tests, and that was just my first time watching it run.
Once again, great product, found a whole mass of leaks I was not aware of (and some that I was)!
You’re more than welcome! I had looked at several memory debugging packages, but most of these required a lot of work to get up and running. Memory Validator on the other hand was easy – no changes to my code, up and running and finding leaks and errors in minutes.
First off, congratulations on this great product of yours. With all these code reviews, I only wish I could use your products more often.
Now, that IS impressive! Talk about customer service! Your tool has been very impressive thus far, making our previous purchases of DevPartner, HeapAgent and Purify a waste. Our application uses so much memory (250MB at startup, 1.4GB during full load), the other tools simply couldn’t handle it. The ability to start and stop data collection is key because of our application’s enormous initialization routine.
The Memory Validator folks (softwareverify.com) were very courteous and helpful. Their tech support quickly jumped on the two bugs I reported. As of today, these issues have been resolved and I can recommend Memory Validator as a good balance between performance and strictness for use with omniorb.
Last week I had the pleasure to attend a conference organised by Cambridge Wireless at Cambridge University Møller Centre, Cambridge. The event was free to […]
Many software engineers and their managers struggle to understand what memory fragmentation is and the effects memory fragmentation can have on the software they produce. […]