lazarus 1.6 fpc3.0.0 slow gdb
lazarus / 12-Debugger

----------------------------------------------------------------------
Michael Collier · 2016-09-04 11:08

Debugging in lazarus has slowed down for me, it seems to take a long
time to do the first step forward from a breakpoint. I noticed this
behavior after upgrading to lazarus 1.6, I'm using fpc 3.0.0.   on
windows, not sure what happens on linux. It can take 20 seconds.

----------------------------------------------------------------------
Thaddy · 2016-09-04 11:43

I do not have that problem (not 20 seconds) under windows or linux.

----------------------------------------------------------------------
Martin_fr · 2016-09-10 10:58

Quoteit seems to take a long time to do the first step forward from a
breakpointTo clarify:
- it takes the normal time to start and reach the breakpoint
- but after the breakpoint it takes very long?

I can't think of anything...

Ensure you use -O- (no opt), or at max -O1.
no smart linking (see wiki debugger setup)

gdb was upgraded, you can download the old one from our sourceforge
site (folder "alternative gdb" inside win32/64)

Maybe antivirus?

Maybe the amount and type of debug info? (though I would expect that
to affect time before the 1st breakpoint).
Check the debug info in all packages, and ensure they are either off,
or match (stabs/dwarf) the project. (or use "additions and overrides"
to force them)
Try if their is a diff between stabs and dwarf (dwarf preferred)

----------------------------------------------------------------------
Michael Collier · 2016-09-16 09:18

Quote from: Martin_fr on September 10, 2016, 12:58:17 pmTo clarify:
- it takes the normal time to start and reach the breakpoint
- but after the breakpoint it takes very long?

That's correct, something else I noticed but not sure if normal..

1. In lazarus Press F9 to start debugging.
2. Wait for application main form to appear.
3. Switch back to lazarus , set a break point in a currently non
executing piece of code.

5. **the application hangs for about 5 seconds **

From what I can remember, setting a breakpoint didn't affect a running
program, unless it is set on a running piece of code that causes an
actual break to occur?

I have set debug options to dwarf, and disabled antivirus.

I'll report back if I notice anything else. I can manage with things
but I'd like to know the cause if possible.