Possible EurekaLog access violation

[algalg]

Hi, we are getting some access violations to the EurekaLog which we think could be caused by eureka it self.

The strange thing is that the Assess violation is always at the same address (in one run) but the call stack is different every time.

The call stack ends in kernel32.dll in many cases and the last line in our code is at the beginning of procedure, inside except … end block or at raise exception.

It is not easy to reproduce it. We have to generate heavy load on our COM+ app to reproduce it.

We have the Catch Handled exception switch on and we are using the exception filtering. Eureka version 6.0.2 and 6.0.7 - behaves the same, Delphi 2006.


How can I send you the ELF file?

Any ideas?

[admin]

You can send it to me as attached file, or (if you prefer) as private email at support@eurekalog.com