Thank you for your answer.

Actually, I have to admit that my question was a bit stupid…
I noticed just after having posted that the answers to my questions were already in the examples of the JCL…

(in stacktrack and threadexcept examples)

I have now a fantastic tool to debug my multithreaded Delphi 6 application ! Whatever the unhandled exception is raised in the main VCL thread or in one of my other threads…

Thank you for your answer anyway.

In the SmartInspect Console (standard forms application), we are calling JclLastExceptStackListToStrings in the application exception event to show/log/handle unhandled exceptions. Not sure if this event is available in Delphi 6 though (although I guess it is).

First be aware I’m using Delphi 6 only…

I tried to use JCLDebug and JCLHookExcept units to log unhandled exceptions of my multithreaded application with a full call stack dump. (Using the JclLastExceptStackList function).

But I noticed that my exception notifier (installed with AddExceptNotifier) is called on EACH exception raised in my application, EVEN IF IT IS ALREADY HANDLED in my code.

But I just want to address unhandled exceptions that make crash one thread of my app, getting the complete call stack dump that lead to the unhandled exception raising.

How can I distinguish unhandled exceptions from handled ones ?

I didn’t found how to do this…

Thanks for any help.

What if I need a JCL stack trace for unhandled exceptions only ?

Thank you.
Pierre-François Culand

Sorry for the late response. Nested exceptions should be covered as well by using the InnerException property as follows:

procedure p1;
begin
  try
    p2;
  except
    // Ugly, but seems to work!
    Exception.RaiseOuterException(Exception.Create('Outer exception'));
  end;
end;

procedure TForm1.Button1Click(Sender: TObject);
var
  Ex: Exception;
begin
  try
    p1;
  except
    on E: Exception do
    begin
      // Should be put in some function:
      Ex := E;
      while Assigned(Ex) do
      begin
        SiMain.LogException(Ex);
        Ex := Ex.InnerException;
      end;
    end;
  end;
end;

I’m not sure which Delphi version first introduced inner exceptions but it’s available in Delphi 2009.

procedure p1;
begin
try
p2;
except
// Custom action, for example rollback database
raise Exception.Create;
end
end;

procedure p2;
begin
// a lot of source lines
// one of them raise an exception
end;

I use JCL with debug dcu’s and logging of stacktrace to a textfile. The bad thing is that the original cause of the exception in p2 is hided. The reality can be even more complicated with several levels of try/except raise. If the new D2009 exception + JCL can solve this and point out the real cause of an exception it would alone be worth to upgrade to D2009.

As for this new StackTrace-framework, I suppose SmartInspect (or a library like the Jcl) could back-port this to older Delphi-versions too (for example via a class helper, or if not available via a Inceptor class on Exception), bringing modern features to older compilers! Just a thought…