Jonathan Neve[Microtec] wrote:
> admin wrote:
>>Jouni Aro wrote:
>>>I am evaluating EurekaLog because of a hard to track problem
>>>related to a COM client that is processing data in "server
>>>threads". Should Eurekalog catch the exceptions also in other than
>>>the main thread?
>>Yes, of course!
>>EurekaLog catches every exception raised from any thread, showing the
>>thread call-stack and the calling thread call-stack (the call-stack
>>of the thread that had runs the exception thread).
>>I hope to have answered to your question, otherwise don't hesitate to
>>recontact to me, ok?
> Yes, I think this can be seen in the video demo that's on the EL
Yes, it seems that EL can track threads and report them very cleverly.
However, I seem to have such a tricky issue that the app just disappears
- and I get no track of it with EL either. I suspect a resource problem
related to COM communications (even on a single threaded version), but I
need to use other ways to locate the reason. The problem is that this
error only appears on another site - and appears only after a 14-hour
Anyway, Eurekalog seems to help in many aspects so now it is just a
question which license will we purchase