Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 5996925
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T00:11:28+00:00 2026-05-23T00:11:28+00:00

I am working in a DLL which sometimes raises unhandled exceptions. I am using

  • 0

I am working in a DLL which sometimes raises unhandled exceptions. I am using madExcept to detect and debug the buggy code, but when I finally deploy my DLL I want include my own global exception handler inside the DLL to log the exceptions.

So the question is how I can set a global exception handler in my Delphi DLL?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T00:11:28+00:00Added an answer on May 23, 2026 at 12:11 am

    The concept of “a global exception handler” doesn’t really exist in DLLs the way it exists in the VCL. To understand why, remember that exceptions propagate by unwinding the stack until they can find a handler. The VCL can install a global exception handler because in a VCL app, everything that happens (excluding startup and shutdown) will have TApplication.Run somewhere in the call stack, and that’s where it puts the exception handler. Since your DLL doesn’t have a single central point like that, you can’t do it that way.

    What you can do is set up a “central exception handler routine” in your DLL somewhere. It should take an Exception object as a parameter. Then do something like this for all your exported routines:

    procedure MyExportedRoutine(param: integer);
    begin
      try
        //do normal stuff
      except
        on E: Exception do
          CentralExeptionHandler(E);
      end;
    end;
    

    That’s really the best you can do, unless you’re using COM. If you’re writing a COM DLL, mark your interface methods with the safecall calling convention and the compiler will silently generate code for you that takes care of exception propagation.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm working on an application so i have write an dll which contain a
I´m working on a project, in Visual Studio 2008, which DLL currently surpasses 20
I'm working on a setup which wants to include the Microsoft.Web.Services3 (WSE 3.0) DLL
I am working on migrating a 32-bit ISAPI dll to 64-bit. I am using
Cdonts is not working in server 2008 (im using 32bit) i tried copying cdonts.dll
I am using setupapi.dll to determine USB device connectivity. It isn't working properly in
I am working on the Visual studio 2010. want to create a dll which
I'm attempting to compile a working copy of the MagickNet class library (DLL) using
I'm working on a DLL which will be used from another language (so no
I am working on a project which uses an import #import progid:Blah.blah.retrieve rename_namespace(Blah) but

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.