[Lazarus] Debugger stops in c dll even when no breakpoint set

Martin Frb lazarus at mfriebe.de
Thu Oct 28 14:46:37 CEST 2021

On 28/10/2021 14:28, Christo Crause via lazarus wrote:
> On Thu, Oct 28, 2021 at 2:01 PM Luca Olivetti via lazarus 
> <lazarus at lists.lazarus-ide.org> wrote:
>     77045AC4 cc                       int3
> The Int3 instruction means break, so this is the expected behaviour.  
> If there is no debugger inserted break point for this location, it 
> must be compiled into the dll code.  This means not stopping here will 
> be problematic, unless you use some kind of script to step over this 
> break instruction automatically.  I do not think it is possible from 
> inside Lazarus, but haven't actually tried to work around something 
> similar before.

FpDebug refers unknown "int3" back to the application, and lets the 
application handle them itself.

At least FpDebug does this by default. There is an option in the global 
settings to stop.
But if the dll expects the int3, and therefore wants to handle it 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20211028/3eab2eca/attachment.html>

More information about the lazarus mailing list