This is the mail archive of the gdb-patches@sourceware.org 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: Move the multi-forks support to the generic multi-inferiors support.


 

> -----Original Message-----
> From: gdb-patches-owner@sourceware.org 
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Pedro Alves
> Sent: June-06-09 12:07 PM
> To: Tom Tromey
> Cc: gdb-patches@sourceware.org
> Subject: Re: Move the multi-forks support to the generic 
> multi-inferiors support.
> 
> On Saturday 06 June 2009 01:07:29, Tom Tromey wrote:
> 
> > How about this?  It adds the column headings and prints 
> something when
> > there are no inferiors.
> 
> This is fine with me, thanks, but,
> 
> are you planning on doing something similar to "info threads" output?
> IMO, both these commands should be consistent.  In that case, you
> may have an issue with MI, as it calls print_thread_info --- I don't
> know if using a table instead of a list changes MI output.

Just a note that up to GDB 6.8, we used the output of "info threads"
in the DSF-GDB Eclipse frontend.  With GDB 7.0 we moved to
"-thread-info"
So, I'm not affected by a change of output, but 
I'm saying this to point out that some frontend may still be using
it and may break when moving to GDB 7.0 if the format changes.
I think CDI-GDB (the older Eclipse GDB frontend) is in that 
category.
I'm not sure if you enforce CLI output backwards compatibility...

Marc

> 
> (I was a bit surprised to (re-)find that MI doesn't use
> print_inferior)
> 
> -- 
> Pedro Alves
> 


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