This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] implements MI "-file-list-exec-sections" (updated)


On Fri, Apr 30, 2004 at 10:53:47PM +0100, Nick Roberts wrote:
> 
> > > > Maybe it's worth mentioning, that GDB/CLI output for "info file" changes
> > > > with this patch which will probably break programs that parse this. (I
> > > > don't think such programs exist)
> 
> > > I get the feeling that changing the CLI output of "info file" is a bad
> > > idea. My hunch is that some front ends to GDB are calling that function.
> 
> > One motivation of MI was to free us of this concern, we have to start
> > somewhere. I should look at this in the morning.
> 
> For information only, please note that gdb-ui.el (CVS Emacs) currently uses
> CLI output from the following commands:
> 
> info source
> info breakpoints
> where
> info threads
> info registers
> info locals
> disassemble
> info frame
> 
> I plan to put a more basic version that uses GDB/MI into CVS as soon as Emacs
> is released, whenever that might be. Andrew, if you are planning to change CLI
> output could you please convey this to Richard Stallman, so that there can be
> some co-ordination of schedule between GDB and Emacs.

I think everyone agrees, changing the CLI would be the worst possible
thing GDB could do. What other options are there?

For some unfortunate reason, every front end would break in some subtle
way if the output of the CLI was modified. In some way, it doesn't
really make sense to just coordinate GDB with Emacs and not every other
front end, right?

Bob Rossi


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]