Debugger Performance regression?

[Andreas Pakulat]

On 14.09.09 09:39:45, Vladimir Prus wrote:
> On Sunday 13 September 2009 Andreas Pakulat wrote:
> 
> > Hi,
> > 
> > just wanted to check wether anybody else as performance problems with
> > current kdevplatform/kdevelop when debugging apps? In particular startup
> > of KDevelop inside KDevelop takes a couple of minutes until the
> > mainwindow is shown. I know this was better some time ago, but can't say
> > since when I haven't tried this.
> > 
> > Vladimir are you aware of any breakages from the recent changes that
> > would create such horrible performance? I've checked the internal
> > commands and during the long waiting time there's no output showing up
> > there...
> 
> Is the disk spinning?

No. But one core is fully loaded with gdb.

> With gdb 6.8, the time between 'run' command in console gdb till the time
> when the kdevelop window appears 0:14. With CVS HEAD gdb, it took 0:26.
> So, some regression did happen. Before I poke gdb developers, can you double-check
> there's no extra delay when debugging using KDevelop, as opposed to console gdb.

Its not starting itself apparently. Just starting kdev from inside kdev
is fast. However it seems to get a lot slower with each Breakpoint I'm
settin on the source code. The attached file shows the gdb-output. Whats
noticeable is that gdb took a break of 30-50 seconds after printing line
140. The stuff before that was visible instantly. Printing out the rest
and showing the KDevelop mainwindow took another 90 seconds or so. With
4 breakpoints set on 3 different plugins and one kdevplatform library.

Doing the same with "pending breakpoints" from gdb commandline seems to
be showing the same problems.

So is this just the old "gdb is horribly slow when needing to check
loaded libs for pending breakpoints"?

Andreas

-- 
Green light in A.M. for new projects.  Red light in P.M. for traffic tickets.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gdb_output.gz
Type: application/octet-stream
Size: 6086 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090914/510dec67/attachment.obj>