: Use madExceptPatch.exe on all your .bpls. This embeds the symbol information so that the main executable's madExcept engine can resolve call stacks across multiple modules without needing external .map files.
Its primary role is to catch unhandled exceptions, generate comprehensive reports (including full call stacks with unit names, function names, and line numbers), and provide options to handle these errors, such as saving reports, emailing them, or restarting the app. Why madExcept is the Top Choice for Delphi Developers
: If you build your application using continuous integration tools or custom command-line MSBuild scripts, use the command-line patch utility. Run the tool directly against your compiled BPLs: madExceptPatch.exe MyCompiledModule.bpl Use code with caution. madexceptbpl top
: You can configure madExcept to periodically check if the main thread is still reacting to messages. If it stays frozen (default 60 seconds), it raises an exception to help you find infinite loops or deadlocks. Resource Leaks "instantly crash on buffer over/underrun"
stack dump: [12345678] madexceptbpl top ... : Use madExceptPatch
The power of madExcept lies in its flexibility. Developers can configure how the BPL interacts with their projects through the madExcept Settings dialog:
To make the most of your madExceptBpl installation, follow these best practices: Why madExcept is the Top Choice for Delphi
A BPL is a specialized DLL that contains VCL components and RTL (Run-Time Library) code. Unlike standard DLLs, BPLs share the memory space of the host application.
Detect memory and resource leaks that slow down or destabilize software over time.
One of the core philosophies of madExcept is the ability to retrieve detailed stack traces from release builds to customers. When madExcept processes the final executable, it embeds the debugging symbol information directly into the binary. If a production crash occurs, the user sends back a report; the developer can then double-click on any line in the stack trace, and the Delphi IDE will automatically jump to the exact line of code in their project that caused the crash. This reduces the Mean Time to Repair (MTTR) from hours of guesswork to seconds of direct navigation.