21
votes

How would you compare MadExcept to EurekaLog as an Exception handler for your Delphi application?

Why would you pick one over the other?

Are there any other exception handlers for Delphi that should be considered in addition to these two?


Well the answer was between Smasher and Mark, who both had good info in their comparisons but ended up picking one and the other. So it was a toss up - and I gave the answer to Smasher, just because he was the first of the two to answer.

6

6 Answers

12
votes

We did compare these two before deciding to use EurekaLog. It looked a lot more configurable and also seems to have the more professional support. Nothing bad to tell about EurekaLog so far. It works great and isn't too hard to set up and configure the way you like it.

11
votes

After comparing the two I went with MadExcept. At the time (~5 years ago) there were some difference that were important to me but looking at their websites now it looks like the feature differences no longer exist.

One of the items that swayed me was Stack Tracking methods on the Madshi site. A previous company I worked for had a custom execption object for VB6. I saw some of the pain they went through and my impression is that Madshi is a really smart guy who knows what he is doing.

I did inherit a project that used EureakLog and actually used both for about 2 years. In the end I converted that project to use MadExcept. I was more comfortable with it and preferred the MadExpect bug reports.

I have had very good luck with support on the Madshi forums - some times with the answer from Madshi himself. If you take a look you will see he is very active there.

I have looked at the JCL stuff, but both MadExcept and EureakLog as so cheap, professional, and work well that I didn't even think twice before going with MadExcept.

8
votes

We are a team that use JCL for catch exceptions and log them with callstack to a log-file. It works fine.

4
votes

JCL has it's own exception handler, it's free of course and it's quite nice.

2
votes

There is also JclDebug, part of the jedi code library. I don't know how it compares to MadExecpt and EurekaLog since I never used any of these two.

1
votes

On a very big project I tried both the trials and I was able to compile at the first attempt with MadExcept while compilation failed wit EurekaLog. My colleague by the way could compile with both, so it was a machine dependant problem. Btw they ship with similar good features, a must have for every company.