If you have ever looked at your project’s runtime packages list, deployed an application, or debugged a "Package not found" error, you have likely encountered madexcept-.bpl . This article explores what this file is, why it exists, how to use it correctly, and how to troubleshoot common issues related to it. 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.
C:\Program Files (x86)\madCollection\madExcept\Bpl\<DelphiVersion>\madexcept-.bpl Or inside your project’s $(BDSCOMMONDIR)\Bpl folder. madexcept-.bpl
Introduction For Delphi and C++Builder developers, ensuring application stability is a critical, often challenging task. When an unexpected exception occurs—especially on a client machine in a production environment—tracking down the root cause can feel like searching for a needle in a haystack. This is where madExcept (by siComponents) becomes an indispensable tool. At the heart of its powerful runtime hooking and exception interception mechanism lies a specific file type: the .bpl (Borland Package Library), most notably referenced as madexcept-.bpl . If you have ever looked at your project’s