Non-custodial Solana crypto wallet for NFTs - Phantom Platform - securely manage tokens and stake rewards.
You can safely ignore this as internal bookkeeping. Focus on the lines above top – those are your actual crash locations. If top is the only line shown, your stack is corrupted, and you need to enable “Copy stack trace as text” and submit it to Madshi forums. Part 5: Best Practices for MadExcept + BPL Projects To avoid ever needing to search for madexceptbpl top again, follow these golden rules:
call TopOfStack -> returned 0x... In poorly symbolized call stacks, this becomes [madexceptbpl] top . madexceptbpl top
In MadExcept settings → "Exception box" → Check "Show on top of all windows" or add the following to your project’s madExceptSettings.mes : You can safely ignore this as internal bookkeeping
madexcept.bpl;vcl.bpl;rtl.bpl;mybusiness.bpl Now MadExcept initializes first, giving it top-level control. A less common but real issue: when an exception occurs, MadExcept shows a modal dialog. If your application has top-most windows (forms with FormStyle := fsStayOnTop ), the MadExcept dialog might get hidden behind them. Searching for madexceptbpl top sometimes leads to posts about "Make MadExcept dialog top-most too." Part 5: Best Practices for MadExcept + BPL
Plugin1.bpl was compiled with MadExcept enabled (embedding its own copy). The main EXE also had MadExcept. The two copies conflicted, and the stack trace was overwritten.
Inside madExcept.pas , there is a function called TopOfStack (or GetTopOfStack ), which returns the highest memory address of the current thread’s stack. When an exception occurs in a BPL, MadExcept sometimes logs the instruction before the crash as:
You can safely ignore this as internal bookkeeping. Focus on the lines above top – those are your actual crash locations. If top is the only line shown, your stack is corrupted, and you need to enable “Copy stack trace as text” and submit it to Madshi forums. Part 5: Best Practices for MadExcept + BPL Projects To avoid ever needing to search for madexceptbpl top again, follow these golden rules:
call TopOfStack -> returned 0x... In poorly symbolized call stacks, this becomes [madexceptbpl] top .
In MadExcept settings → "Exception box" → Check "Show on top of all windows" or add the following to your project’s madExceptSettings.mes :
madexcept.bpl;vcl.bpl;rtl.bpl;mybusiness.bpl Now MadExcept initializes first, giving it top-level control. A less common but real issue: when an exception occurs, MadExcept shows a modal dialog. If your application has top-most windows (forms with FormStyle := fsStayOnTop ), the MadExcept dialog might get hidden behind them. Searching for madexceptbpl top sometimes leads to posts about "Make MadExcept dialog top-most too."
Plugin1.bpl was compiled with MadExcept enabled (embedding its own copy). The main EXE also had MadExcept. The two copies conflicted, and the stack trace was overwritten.
Inside madExcept.pas , there is a function called TopOfStack (or GetTopOfStack ), which returns the highest memory address of the current thread’s stack. When an exception occurs in a BPL, MadExcept sometimes logs the instruction before the crash as:
