...handle an exception?

Important note for C++ Builder users: see How to handle a C++ exception?

Important: as a general rule, you should write your application in a such way that it will behave correctly without EurekaLog on board. This means that if your or 3rd party code throws an exception - it must be handled in a way that you expect. For example, by showing an error message, canceling action, retrying, etc. Once your application behaves like it is supposed to do - then you add EurekaLog for it. EurekaLog will auto-handle all unhandled exceptions automatically (by hooking few well-known places), and for everything else - you can call EurekaLog from your own handlers when needed. In other words:

EurekaLog automatically catches any unhandled exceptions in your application. However, you may want to force-handle exception coming from a specific code:

try
  // ... some code ...
except
  on E: ENetworkError do
  begin
    // How to handle this?
  end;
end;

If this is the case - then you can use any of the following:

For example:

try
  // ... some code ...
except
  on E: ENetworkError do
    Application.HandleException(nil);
end;

or:

try
  // ... some code ...
except
  on E: ENetworkError do
    ApplicationShowException(E);
end;

This code will show a usual error message box when EurekaLog is not enabled/active, but it will show full EurekaLog's dialog (with call stack, sending, etc.) when EurekaLog is enabled and active.

Notes:

Important Notes:

See also: