Which Exception Analyzer do you use?

Which Exception Analyzer do you use?

What are the main benefits of your choice?  

Does it submit a report to your error tracking tools?

Which features do you find lacking in your current tool?

(Image courtesy of Google image search)

25 thoughts on “Which Exception Analyzer do you use?


  1. We use a JclDebug-based  solution. I modified some parts so that it uses bzip2 to compress the binary debug info to reduce space used (from 2-3MB to <1MB IIRC).


    I’ve then written a function to log the stack traces to a log file in the installation’s log directory. Unhandled exceptions gets logged this way, along with unexpected exceptions during integrations where we need to trap most exceptions while trying to keep on chugging.


    We usually only look at them if a customer reports an error.


    We already have a webservice for providing updated code lists and similar to customers, I’ve been thinking about using it to upload stack traces so we can more easily spot issues before the customers get annoyed, as well as more easily spot patterns. Only on the planning stage in my head for now…


  2. I was using EurekaLog but have switched to madExcept few years ago due to the performance issue. But I DO have a complain with madExcept – in this large screen ages, the font size it uses for its error reporting UI is way too small that it hurts my eyes!


  3. Lars Fosdal pre-Seattle it is mainly madExcept. Sometimes it is EurekaLog – it depends which project I work on uses.


    For Seattle, I am currently using JclDebug, as it is the only one (I know of currently) that is Seattle ready (found out that JclDebug doesn’t play well within IDE plug-ins, as conflicts with exceptiondiag230.bpl, which is JclDebug behind the scenes).


  4.  


    I was using EurekaLog but have switched to madExcept few years ago due to the performance issue and incorrect error reporting.  Excellent support for the very few questions I have had.


  5. I use MadExcept. Unfortunatly it is the only critical third-party tool I have that I can’t just re-build for a new version of Delphi. I feel like my project is held hostage until he finishes the new version, LOL.


  6. Brandon Staggs It’s usually not too difficult to make ME work on a new Delphi. But then I don’t use any of the IDE stuff. Just include the source in my project, and script the post-build patching. Which is a better way to work anyway because you use the same build process for interactive and command line builds.


  7. We are using JclDebug and log to SmartInspect. A dialog, similar to the one in the picture displays error info including a stack trace. No, it does not submit an error report to our error tracking tool, especially since we don’t have one. Usually I get bug reports via email including a bloody screenshot of the error dialog pasted into a word document. (It’s easily possible to copy the whole text of the error dialog to the clipboard, but our users seem to be incapable of that.)


  8. +Thomas ME will give you a screenshot with only your app’s windows, and attach it to an email with the bug report. User just has to click send. That screenshot is useful.


  9. David Heffernan Thanks for the tip. It had not even occurred to me to try using my current ME on an D10 project but I will. I do use the design-time component so I also need to get the package added which is why I typically just wait.


  10. And my favorite feature is double clicking on a stacktrace item will get me straight to the source code if the project is currently opened in the IDE. Not sure if I’m the first one, but I think I suggested that feature to the madExcept author when I was switching away from eurekaLog 🙂


  11. I love madExcept’s easy setup with Mantis. I got tired of so many customers not having MAPI functional on their computers so I installed Mantis (made some minor modifications to lock it down a bit) and MadExcept just uploads bug reports right into the database.

Leave a Reply