[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-devel
Subject: Re: Improving variables view
From: Alexander Neundorf <neundorf () kde ! org>
Date: 2005-06-10 19:21:57
Message-ID: 200506102121.57323.neundorf () kde ! org
[Download RAW message or body]
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;
actOnProgramPause(QString(buf));
return;
}
kdDebug(9012) << "Unparsed (default - busy)<" << buf << ">" << endl;
actOnProgramPause(QString());
return;
}
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.
Bye
Alex
--
Work: alexander.neundorf@jenoptik.com - http://www.jenoptik-los.de
Home: neundorf@kde.org - http://www.kde.org
alex@neundorf.net - http://www.neundorf.net
_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic