Recent

Author Topic: lazarus 1.6 fpc3.0.0 slow gdb  (Read 3790 times)

Michael Collier

  • Sr. Member
  • ****
  • Posts: 301
lazarus 1.6 fpc3.0.0 slow gdb
« on: September 04, 2016, 01:08:30 pm »
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

  • Hero Member
  • *****
  • Posts: 14197
  • Probably until I exterminate Putin.
Re: lazarus 1.6 fpc3.0.0 slow gdb
« Reply #1 on: September 04, 2016, 01:43:25 pm »
I do not have that problem (not 20 seconds) under windows or linux.
Specialize a type, not a var.

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9791
  • Debugger - SynEdit - and more
    • wiki
Re: lazarus 1.6 fpc3.0.0 slow gdb
« Reply #2 on: September 10, 2016, 12:58:17 pm »
Quote
it seems to take a long time to do the first step forward from a breakpoint
To 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

  • Sr. Member
  • ****
  • Posts: 301
Re: lazarus 1.6 fpc3.0.0 slow gdb
« Reply #3 on: September 16, 2016, 11:18:39 am »
To 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.


 

TinyPortal © 2005-2018