Improving variables view

Alexander Neundorf neundorf at
Fri Jun 10 21:23:06 UTC 2005

On Wednesday 08 June 2005 11:36, jbb wrote:
> It's trying to filter out lines that fall out of gdb we didn't ask for.
> This piece of history and it's associated problems would be consigned to
> the bit bucket if MI was used. It could also be reworked easily to avoid
> your paticular pitfall. Try the patch - it's untested... the same sort of
> changes could be done throughout this method.

Yes, and it should be, especially since there's a final "catch all" clause:

// Any other line that falls out when we are busy is a stop. We
// might blank a previous message or display this message
if (stateIsOn(s_appBusy))
    if ((strncmp(buf, "No ", 3)==0) && strstr(buf, "not meaningful"))
        kdDebug(9012) << "Parsed (not meaningful)<" << buf <<  ">" << endl;
    kdDebug(9012) << "Unparsed (default - busy)<" << buf << ">" << endl;

which really catches all other lines :-/
I'm not sure if I can simply disable all these tests, I guess you had a reason 
to write them this way.

Another pro for the MI mode: when downloading the file e.g. over the serial 
line to the target, you get progress messages in MI mode, which could be used 
to provide a nice progress bar.

Work: alexander.neundorf at -
Home: neundorf at                -
      alex at               -

More information about the KDevelop-devel mailing list