Madexcept-.bpl

Demystifying madExcept.bpl: The Powerhouse Behind Delphi Exception Handling

If you are a Delphi developer, or if you have stumbled upon this file while debugging an application, you have likely encountered madExcept.bpl. To the uninitiated, it might look like just another cryptic file in the system32 or application directory. However, for developers using the MadExcept library, this file is the linchpin of robust error reporting.

In this post, we will break down what madExcept.bpl is, why it is essential for Delphi programming, and how to troubleshoot common issues associated with it.

Breaking Down the Name

| Part | Meaning | |------|---------| | madexcept | The core madExcept package name. | | - | Separator between package name and platform suffix. | | .bpl | Borland Package Library—a Delphi runtime package (similar to DLL but for VCL components). |

In older versions (before madExcept 5), you might see names like madexcept_D12.bpl (where D12 means Delphi 12). In modern versions, the dash convention applies, and you may encounter: madexcept-.bpl

• madexcept.bpl – Standard runtime package.
• madexcept-.bpl – A specific build (e.g., without debug info or with certain conditional defines).

Important: madexcept-.bpl is not a typo. The trailing hyphen is intentional and signals a particular compilation configuration—typically a release build without debug RTL or with stripped symbols.

---

What is madExcept? A Quick Refresher

Before dissecting the .bpl, it is important to understand the tool. madExcept is a commercial exception tracing and logging library for Delphi and C++Builder. It hooks deeply into the VCL (Visual Component Library) and RTL (Run-Time Library) to catch any exception—whether a simple EAccessViolation, a resource leak, or even a terminated thread.

When an exception slips through, madExcept automatically generates a detailed bug report containing: Demystifying madExcept

• Call stack with line numbers.
• CPU register dump.
• Thread list and stack traces.
• Module (DLL/EXE) version information.
• Screenshot of the user’s desktop (optional).
• Screenshots of all open forms.

The library can be integrated either directly into your main executable (static linking) or via runtime packages (.bpl files). The latter approach produces the madexcept-.bpl file.

---

For End Users

If you see madexcept-.bpl running in your task manager or temp folders, it means an application you are running was built with Delphi and uses the MadExcept framework.

• If the application is running smoothly, this file is working in the background to ensure stability.
• If the application crashed, this file helps generate the "Send Error Report" dialog you see on screen.

Solution: Deploy madexcept-.bpl Correctly

Find the file on your development machine. It is typically located at: madexcept

C:\Program Files (x86)\madCollection\madExcept\Bpl\<DelphiVersion>\madexcept-.bpl

Or inside your project’s $(BDSCOMMONDIR)\Bpl folder.

Copy this file to the same folder as your application’s .exe on the target machine. No registration or COM activation is required.