disappointed

[mickeyf]

I have decided not to use and have uninstalled Eurekalog trial. It looked promising, but I exercised my application automatically for a continous week and Eurekalog did not catch a single bug. Very very occasionally the program entirely crashes and blues screens, but when this occurs Eurekalog entirely misses it. This appears to be an issue with USB modems and Windows XP - it does not seem to occur with other combinations (i.e. Win 2K is fine with USB modems and non-USB modems are fine with any version of Windows. My hope was the Eurekalog would help with the obscure, hard to track down bugs like this. The easy ones are ... easy.

[admin]

Hi,

mickeyf wrote:
> I have decided not to use and have uninstalled Eurekalog trial. It
> looked promising, but I exercised my application automatically for a
> continous week and Eurekalog did not catch a single bug. Very very
> occasionally the program entirely crashes and blues screens, but when
> this occurs Eurekalog entirely misses it. This appears to be an issue
> with USB modems and Windows XP - it does not seem to occur with other
> combinations (i.e. Win 2K is fine with USB modems and non-USB modems
> are fine with any version of Windows. My hope was the Eurekalog would
> help with the obscure, hard to track down bugs like this. The easy ones
> are ... easy.

I'm sorry but this isn't an EurekaLog limit but an OS limit.

When Windows crashes with a blues screen it's a kernel OS exception so
it's impossible for a non-OS software detect it.

Probably your software create a situation able to raise a OS kernel
exception.

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!

[Jouni Aro]

admin wrote:
> Hi,
>
> mickeyf wrote:
>
>> I have decided not to use and have uninstalled Eurekalog trial. It
>> looked promising, but I exercised my application automatically for a
>> continous week and Eurekalog did not catch a single bug. Very very
>> occasionally the program entirely crashes and blues screens, but when
>> this occurs Eurekalog entirely misses it. This appears to be an issue
>> with USB modems and Windows XP - it does not seem to occur with other
>> combinations (i.e. Win 2K is fine with USB modems and non-USB modems
>> are fine with any version of Windows. My hope was the Eurekalog would
>> help with the obscure, hard to track down bugs like this. The easy ones
>> are ... easy.
>
>
> I'm sorry but this isn't an EurekaLog limit but an OS limit.
>
> When Windows crashes with a blues screen it's a kernel OS exception so
> it's impossible for a non-OS software detect it.
>
> Probably your software create a situation able to raise a OS kernel
> exception.

That's right: there are several issues, which I understand very well
that are limited by the OS and it is very difiicult (most probably
impossible) to intervene in that. EL cannot track everything - and it's
value is that it points you to the cause of a problem more directly than
you get without it.

I also had hard to track issues where EL did not help, but I decided to
purchase it just now in any case. The side effect is that I nowadays get
more reports from the Delphi 7 IDE than I did before. Unfortunately
those tell only about ntdll or rtl problems instead of our own problems
(which I always suspect but very rarely get a proof).

We have also developed an instrumentation based debug logging, which can
help with the most difficult problems. Although you can't catch the
exception, you get a log of the recent events, which helps you to track
the roots. Mickey, I recommend you try one of this kind of logging with
your problem, too.

Our "Prosys Debugs" is available at
http://www.prosys.fi/downloads/Debugs.zip (including the source and a
Windows Help). There is a also a viewer under development, but you will
normally do just fine by examining the logs with a standard text viewer.
There are other products also available...

BTW: Our debugger also catches exceptions using the global 'ExceptProc'
and 'SetUnhandledExceptionFilter', which catch run time errors occuring
outside the Delphi exception handling mechanism. Does EL use these, too?

[admin]

Jouni Aro wrote:

> admin wrote:
>> Hi,
>>
>> mickeyf wrote:
>>
>>> [...]
>
> I also had hard to track issues where EL did not help, but I decided to
> purchase it just now in any case. The side effect is that I nowadays get
> more reports from the Delphi 7 IDE than I did before. Unfortunately
> those tell only about ntdll or rtl problems instead of our own problems
> (which I always suspect but very rarely get a proof).
>
> [...]

Set to 0 the "C:\Windows\EurekaLog.ini" "IDE\Enabled" value to disable
the EurekaLog IDE integration.

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!