2012/9/11 <[email protected]>

> > -----Original Message-----
> > [...]
> > Does anyone else see the slowness when first executing "run"
> > when debugging a Qt gui application with gdb?
> >
> > Can anyone proactively confirm that the slowness does not occur with some
> > specific mingw-w64 build (preferably 4.7.0 or later) when using gdb to
> debug
> > a Qt gui application built with that mingw-w64 build?  If so, what
> mingw-w64
> > build would that be?
>
>
>
> I just tried debugging a basic Qt console application with both
> mingw64-gcc-4.7.1-2-rubenvb and Mingw-builds-4.7.1 (both 64 bit native) in
> Qt Creator: The gdb from Ruben's build is indeed much slower.  It takes 12
> seconds from startup to hitting a breakpoint in main.cpp, compared to 4
> seconds with the gdb from niXman.  Digging further, the `-break-insert
> "\"main.cpp\":5"` that's executed on startup from Ruben's build takes 6,7
> seconds to return, while it's only 1,4 seconds for mingw-builds. But we're
> sending the commands interleaved, so it might be that the -break-insert
> response is delayed by other commands, too ...
>
> So yes, something's fishy here.  Both are using a quite similar gdb
> version: 7.5.50.20120816-cvs (rubenv's) vs 7.5 (mingw-builds). The only
> other difference from the log is that rubenv's gdb also prints some
> '=cmd-param-changed,param="' messages, while mingw-builds does not.
>

Thanks for the detailed analysis. This at least gives me something to
compare to and find what might be causing this. I bet it's as simple as a
gdb configure option or something.

I'll take a look at this when I'm back home.

Ruben


> Regards
>
> Kai
>
>
> > > Ruben
> > >
> > > PS: I obviously vote for my builds as at least a base for the "Qt
> > > toolchain". I will be glad to help in an effort to build/maintain such
> > > a thing.
> >
> > I also vote for using Ruben's builds for the "Qt toolchain."  This is
> purely selfish
> > on my part, but I've been having good results with Ruben's builds, and
> if Qt
> > happens to choose the same compiler that I'm using, then I would be able
> to
> > experiment more easily with new versions of Qt, because I wouldn't have
> to
> > build Qt myself.
> >
> > Thanks in advance for any information / solutions on the gdb slowness
> > problem.
> >
> >
> > K. Frank
> >
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and threat
> > landscape has changed and how IT managers can respond. Discussions will
> > include endpoint security, mobile security and the latest in malware
> threats.
> > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Mingw-w64-public mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Mingw-w64-public mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to