KDevelop 3.4 RC 1

[Vladimir Prus]

On Saturday 14 October 2006 06:19, Hamish Rodda wrote:
> On Saturday 14 October 2006 06:35, Vladimir Prus wrote:
> > On Saturday 14 October 2006 00:01, Andreas Pakulat wrote:
> > > On 13.10.06 11:51:42, Matt Rogers wrote:
> > > > How stable has the new QMake stuff become? Are we getting enough
> > > > useful feedback from our testers to get bugs fixed?
> > >
> > > Yes, Stephan Diedrich is currently very active and I guess once I ping
> > > geiseri again I can get some support from him too. However there are
> > > still some things on my todo list.
> > >
> > > > Same questions for the code completion.
> > >
> > > More important IMHO: Debugging, there are afaik still some problems
> > > with the debugger, the most annoying at the moment is that it tries to
> > > acces 0-pointers and variables that are not initialized at the current
> > > code line..
> >
> > I'll try to look into 0-pointers issue and the slowness on deep stacks
> > this weekend.
> >
> > What's up with uninitialized variables, I don't recall being told about
> > that.
>
> Sometimes if you enter a context with a QString which is not defined until
> later, gdb tries to access the uninitialised string when we issue a print
> statement and seems to get stuck.  I'm not sure what we can really do about
> this though.

Yes, that is the know issue -- we have no way to tell if QString is 
initialized or not, so must emit the command to print it. It's news to me 
that it kills  gdb, though.

-  Volodya