Yahoo Serious
2008-06-20 13:35:43 UTC
I just started using JCL to log the call stack for Exceptions. To ignore
the 'normal' Indy Exceptions I use AddIgnoredException(EIdException),
because they should be handled in the regular program flow.
However, Indy's IdGlobal.SetThreadName uses RaiseException(...). This
Exception seems necessary to do the job. Like any Exception this does
trigger JCL to log the call stack. I am wondering whether it is possible to
use a 'typed' Exception, inheriting from EIdException?
(I have no knowledge at all about RaiseException, so I have no idea wether
this is possible/easy.)
(Another option would be to use JCL's stDelayedTrace, which prevents JCL
from resolving the call stack until asked for it. However, this will have
no resolution for intermediately unloaded modules.)
Yahoo.
the 'normal' Indy Exceptions I use AddIgnoredException(EIdException),
because they should be handled in the regular program flow.
However, Indy's IdGlobal.SetThreadName uses RaiseException(...). This
Exception seems necessary to do the job. Like any Exception this does
trigger JCL to log the call stack. I am wondering whether it is possible to
use a 'typed' Exception, inheriting from EIdException?
(I have no knowledge at all about RaiseException, so I have no idea wether
this is possible/easy.)
(Another option would be to use JCL's stDelayedTrace, which prevents JCL
from resolving the call stack until asked for it. However, this will have
no resolution for intermediately unloaded modules.)
Yahoo.