From kdevelop-devel Mon Apr 05 08:25:33 2004 From: Roberto Raggi Date: Mon, 05 Apr 2004 08:25:33 +0000 To: kdevelop-devel Subject: Re: improving the debugger for kdevelop 4?? Message-Id: <200404051025.34207.roberto () kdevelop ! org> X-MARC-Message: https://marc.info/?l=kdevelop-devel&m=108115367905061 Hi John! On Sunday 04 April 2004 12:30, jbb wrote: > Good work > > But... > Given that we can already parse gdb output what is the advantage of using > MI? well seems that GDB/MI is really powerful. I don't know how much stable is the interface, but many IDEs already uses it(like eclipse), so maybe it's not to hard maintain code based on it ;) anyway, what I would like to change in our GDB support is the code like if (strstr(buf, i18n("No such file or directory.").local8Bit()) ... else ... I'm afraid that the output messages produced by GDB can change in future, so we will have problems while updating(BUT maybe this isn't true, since the GDB/MI iface has changed while the output messages not). I really don't know if it is a good idea to switch to GDB/MI, for this reason I wrote this prototype, just for checking ;) ciao robe > > Pro > . MI should be stable across future versions > . IIRC it has mixed source and assembly output > . fill in the blanks here > > Con > . MI has changed from it's early versions, why think it won't in the > future? (the cynic in me :-) > . It's not human readable. > . It's a bit of work (but not huge) > . fill in the blanks here > > Most (if not all) of the features that people want are really to do with > the UI not with parsing the output. (tool tips is the most obvious) > > Can you tell us why this will help us? I'm not against doing this but it > just seems unnecessary which is why I've not bothered. Note that thinking > this could be fun to do _is_ a valid reason :-) > > jbb > > On Fri, 02 Apr 2004 20:30, Roberto Raggi wrote: > > Hi! > > > > a few days ago I've discovered the new GDB/MI interface of gdb > > (info:/gdb/gdb/mi).. the new GDB/MI interface seems very easy to parse, > > so maybe we can replace/extend the gdb parser in our debugger with > > something new!! anyway, I wrote a small *prototype* for a GDB/MI > > parser(please, find it in attachment to this email. it is less than 8KB), > > so at least we can start to investigate ;) > > > > ciao robe > > _______________________________________________ > Kdevelop-devel mailing list > Kdevelop-devel@barney.cs.uni-potsdam.de > http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel _______________________________________________ Kdevelop-devel mailing list Kdevelop-devel@barney.cs.uni-potsdam.de http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel