Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2019-05

Self-set breakpoint on a procedure?

3 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Pedro Restrepo

I have been using Lazarus IDE v2.0.0 r60307 with fpc 3.0.4 on a 64bit Windows 10 machine without major issues. However, the debugger inserted a breakpoint on the first procedure in the Implementation section. There are no breakpoints in the procedure. In fact, I wrote a dummy procedure without any body, just the begin and end statements besides the procedure name, and call it during the form activation.

Is there any way to clear that breakpoint? If I remove that procedure, the debugger will stop at the procedure that becomes the first one after the removal of the dummy procedure.
Debugger options:
[image: image.png]
Other options:
C:\lazarus\fpc\3.0.4\bin\x86_64-win64\fpc.exe
-MObjFPC
-Scaghi
-CirotR
-O1
-g
-gl
-gv
-Xg
-WG
-l
-vewnhibq
-Filib\x86_64-win64
-Fu..\LMath\uRegression\lib\x86_64-win64
-Fu..\LMath\UOptimum\lib\x86_64-win64
-Fu..\LMath\UPolinoms\lib\x86_64-win64
-Fu..\LMath\UMathStat\lib\x86_64-win64
-Fu..\LMath\URandoms\lib\x86_64-win64
-Fu..\LMath\uMathUtils\lib\x86_64-win64
-Fu..\LMath\ULineAlgebra\lib\x86_64-win64
-Fu..\LMath\UGenMath\lib\x86_64-win64
-FuC:\lazarus\components\bgrabitmap-9.9.3\bgrabitmap\lib\x86_64-win64\3.0.4 -FuC:\lazarus\lcl\units\x86_64-win64\win32
-FuC:\lazarus\lcl\units\x86_64-win64
-FuC:\lazarus\components\lazutils\lib\x86_64-win64 -FuC:\lazarus\packager\units\x86_64-win64
-Fu.
-FUlib\x86_64-win64
-FE.
-oBaroScanWin.exe
-dLCL

Is this documented anywhere? I can't find any mention on the web or on the documentation.

Any help will be appreciated.

Pedro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20190508/c1411c35/attachment-0001.html> -------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 23062 bytes
Desc: not available
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20190508/c1411c35/attachment-0001.png>

Reply by email

Martin Frb
to Pedro Restrepo
Pedro Restrepo wrote 11 lines
I have been using Lazarus IDE v2.0.0 r60307 with fpc 3.0.4  on a 64bit Windows 10 machine without major issues. However, the debugger inserted a breakpoint on the first procedure in the Implementation section. There are no breakpoints in the procedure. In fact, I wrote a dummy procedure without any body, just the begin and end statements besides the procedure name, and call it during the form activation. Is there any way to clear that breakpoint? If I remove that procedure, the debugger will stop at the procedure that becomes the first one after the removal of the dummy procedure.

You may have a breakpoint in the interface section.

A breakpoint on a none code line, acts on the next code line found. A breakpoint in the interface section (none code), acts where?

This is helpful, if the breakpoint is on an empty line, just ONE line above the code. But not helpful if it is 100 lines above.... It is a gdb "feature", and as of yet we have no workaround.

You can also use the breakpoint window to find breakpoints...

Reply by email

Pedro Restrepo
to Martin Frb

Thank you very much Martin. Yes, there was a breakpoint in the interface section. I found it with the breakpoint window. Probably was the result of an accidental key stroke. I removed it and the issue is gone.

Best regards,

Pedro

On Wed, May 8, 2019 at 1:17 PM Martin Frb via lazarus <

Show quoted text 31 lines
wrote: On 08/05/2019 19:33, Pedro Restrepo via lazarus wrote: > I have been using Lazarus IDE v2.0.0 r60307 with fpc 3.0.4 on a 64bit > Windows 10 machine without major issues. However, the debugger > inserted a breakpoint on the first procedure in the Implementation > section. There are no breakpoints in the procedure. In fact, I wrote a > dummy procedure without any body, just the begin and end statements > besides the procedure name, and call it during the form activation. > > Is there any way to clear that breakpoint? If I remove that procedure, > the debugger will stop at the procedure that becomes the first one > after the removal of the dummy procedure. > You may have a breakpoint in the interface section. A breakpoint on a none code line, acts on the next code line found. A breakpoint in the interface section (none code), acts where? This is helpful, if the breakpoint is on an empty line, just ONE line above the code. But not helpful if it is 100 lines above.... It is a gdb "feature", and as of yet we have no workaround. You can also use the breakpoint window to find breakpoints... -- _______________________________________________ lazarus mailing list https://lists.lazarus-ide.org/listinfo/lazarus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20190508/8f281d08/attachment.html>

Reply by email