Just a few weeks ago we formed a partnership with EurekaLab, the developers behind EurekaLog, the popular exception reporting tool for Delphi and C++Builder. What’s EurekaLog? EurekaLog allows you to catch exceptions and memory leaks, generates a detailed call stack and optionally notifies you via email about any errors your customers experience. More information about EurekaLog:
Additionally, with the help of the new SmartInspect memory protocol, you can conveniently attach SmartInspect log files to EurekaLog exception reports and find out what exactly happened before an exception occurred.
Why did we partner with EurekaLog? The first reason is that both products, SmartInspect and EurekaLog, have a similar customer base – developers who care about the quality of their software. This gives both companies the opportunity to expand their market.
The second reason is that SmartInspect is even more useful if it’s used together with a good exception reporting mechanism. This allows developers to automatically receive SmartInspect log files in case of a crash.
2 Comments
Any chance of functionality like this for madExcept? I have nothing against EurekaLog, I’ve just been using madExcept for so long that I’d prefer not having to swap everything out.
Hello Shawn,
You can use madExcept together with SmartInspect without any limitations (including the memory protocol) and in fact, we haven’t built anything special for EurekaLog. The partnership focuses on promoting each others tools, but there is nothing that prevents madExcept users from using SmartInspect (and we support this, too, of course). Here is a quick introduction to the memory protocol of SmartInspect and more is available in our online documentation:
http://blog.gurock.com/postings/new-memory-protocol-in-smartinspect-20/229/