Yet another EurekaLog bug. How many until now?

I stepped last week in a multiple-bug situation with EurekaLog for Delphi. I again wasted MORE than a day with this buggy "exception tracer tool".

My DRP file is like this:

PROGRAM MyProgram;
uses
  {$ifdef win32}fastmm4,{$endif}
  EurekaLog_units_come_here

This worked fine until I compiled the program to 64 bits.
On 64 bit, EurekaLog refused to work. After lots of emails exchanged with their (slow) customer support I got NOTHING.
In the end I have found the problem: a bug (oh yes, another one) in EurekaLog. Eureka v7.4 could not properly parse the DRP file when it contains conditional directives like {$ifdef}.
So, because EurekaLog parse my dpr file was like this

 
PROGRAM MyProgram;
uses
  {$ifdef win32}fastmm4,
  EurekaLog_units_come_here
  {$endif}

Solution? None. The support guy from EurekaLog (Alex) invided me to pay for a new license on order to get a small update (same version, so update, no upgrade) to v7.5 which allegedly works. I won't do that. I should receive the UPDATE to the non-bugged version for free AT LEAST for the reason that I have invested time to help them locate the bug.

________________

Maybe they should write a bug tracker tool for their one bug tracker tool :)

How to configure EurekaLog to send bugs via email

Email sender settings in EurekaLog v7
 

	SMTP Server [1]	Simple MAPI	MAPI	Shell (MailTo)	SMTP client [3]
Can attach the ELP file	Yes	Yes [2]	Yes [2]	No	Yes
See sender's email	No [4]	Yes	Yes	Yes	No
Email client software*	Not required	Required	Required	Required	Not required
Chance of success	Highest chance among all methods	High if email client installed	WinMail & Outlook only!!	High if email client installed	I get a 'revocation function' error but for others is working
Can tell if email was successfully sent?	No	Yes	Yes	Yes	Yes

1 - Many antivirus products will flag your EXE as virus

2 - if "Append bug report text in the message text" is UNCHECKED

3 - Typically, you should use either SMTP server or SMTP client, but not both methods simultaneously.
Bugged in EurekaLog v7.4.8.0 RC 1 - Error code = -2146885613 - The revocation function was unable to check revocation because the revocation server was offline. Maybe because: “Currently EurekaLog supports AUTH LOGIN and AUTH PLAIN authentication methods”?

4 - could be enabled via SetUserEMail function)

* If required: Email client must be installed and properly reconfigured. User must to click on "Send" in their e-mail clients. Automatic send without user actions is not possible. 

_____________ 

Please note that EurekaLog v7 is also plagued with several serious bugs! I contacted the producer but he didn't bother to reply until now.