Too many message boxes from the debugger in kdev3.4

[Vladimir Prus]

On Sunday 10 September 2006 16:26, Andreas Pakulat wrote:
> Hi,

Andreas, I'm bringing this on-list.

>
> another thing with the debugger, which I want to discuss with you before
> filing a bug report: The debugger is IMHO too noisy.
>
> While it might be really great to have message boxes pop up whenever the
> debugger can't access a variable or smth. like that, it's certainly very
> annoying to have to click them away when you want to debug something.
>
> Curerntly for the following snippet of code I get 3 msg. boxes on every
> single step:
>
>             QMake::AssignmentAST * s = static_cast<QMake::AssignmentAST*>(
> *it ); if ( s->scopedID == "SUBDIRS" )
>             {
>                 for ( QStringList::const_iterator sit = s->values.begin();
> sit != s->values.end() ; ++sit ) {
>                     if ( *sit != "\n" && *sit != "\\\n" &&
> m_subProjects.contains( *sit ) ) result.append( m_subProjects[ *sit ] );
>                 }
>             }
>
> The first one says that s isn't an lvalue and can't be accessed. The
> other two are telling me that the debugger can't access memory address
> 0x0.
>
> I've seen other places where it's the same. Sometimes for example when
> trying to walk through the data in a Qt valuelist or similar things I
> get msg. boxes telling me that it can't acess the variables... (I don't
> have an example at hand).
>
> Is there currently a way to disable this? If not I think this would make
> a good option in the debugger settings, something like: verbose debugger
> error messages as a checkbox.

Every such message is either bug in gdb, or in KDevelop code, so if you can 
report them using self-contained projects, that would be great. 

- Volodya