Jeremy Pullicino wrote: The product does live up to most of what it promises - I really like the way you could learn how to use the program in beginner, intermediate and advanced mode. Thank you. We added this in response to user requests. It was up, running and debugging within minuites and had little impact on my applications. Thank you. However, I did click on a feature (some memory view .. I forgot), and i got a crash screen (detected by mem validator). We've recently fixed a variety of bugs, and implemented new features for a customer. I notice that you have not contacted us describing the bug. If you had, we probably could have got you a bug fix within a day or so (our fastest bug turnaround is 4 hours, slowest is 1.5 weeks). There was a button whcih would enable me to copy the error report, however, the dialog was crashed also. Thats just bad luck, when an app is crashed you've no idea whats been messed with, and the button uses the clipboard functions and getting the dialog up uses the C++ heap, so there is plenty of scope for it to go wrong at this point. The head of the testing labs liked the product very much, but thinks it might be too complicated for the testers since we are only interested in them detecting that a leak exists, nothing more. I'm confused, as this is trivial to with Memory Validator. Just start your app, run it until completion. Memory Validator shows you leaked memory in the leaked colour (default is yellow). What could be easier?
You can also run it from the command line, so you can embed the entire process in a script so your testers don't even need to point and click on anything in Memory Validator.
Please contact me at support@softwareverify.com, I'll be happy to write new tutorials covering any topics your testers require. Stephen Kellett -- Memory Validator. Faster Leak Detection, Better Analysis. http://www.softwareverify.com http://www.objmedia.demon.co.uk/rsi.html