[Lazarus] Invisible Breakpoint

Martin Frb lazarus at mfriebe.de
Wed Jun 24 20:12:23 CEST 2015

On 24/06/2015 19:05, aradeonas wrote:
> Take a look at attachment,as you see blue dots are at all lines except 
> the procedure that breakpoint is in it.Also as you can see debugger 
> wait on 303.
>     BEst to open an issue on the bugtracker
> Yes but I have problem to reproduce it.

Ah, that looks like a different issue. There are no blue dots for that 
procedure at all. That usually means this procedure was not compiled 
into the exe at all.

If the procedure is not in the exe, then gdb thinks there is no 
executable code on that line 291, and it sets the breakpoint on the 
first line with code that it can find after that. (Yep in that case it 
be better to not set a breakpoint at all, and mark the breakpoint as 
invalid, but that is not (yet) implemented).

By any chance, do you have smart linking enabled?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20150624/9135372c/attachment-0003.html>

More information about the Lazarus mailing list