Delphi packages are tricky. Unlike standard DLLs, BPLs are designed to share the same memory manager, classes, and RTTI (Run-Time Type Information) as the host executable. When a crash occurs inside a loaded package, madExcept must determine if the crash address falls within the boundaries of a loaded BPL.

Developers interacting with madExceptBpl often face two specific scenarios:

call TopOfStack -> returned 0x...

A few possibilities:

By mastering these techniques, you turn MadExcept from a source of cryptic log entries into your most powerful ally for building rock-solid Delphi applications – no matter how many BPLs you load.

When building large applications in Delphi, developers often split code into to reduce executable size and improve modularity. However, this creates a challenge for error reporting: if an exception occurs inside a package, the stack trace might only show memory addresses rather than actual function names or line numbers.