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.


>>>>> "Marc" == Marc Khouzam <marc.khouzam@ericsson.com> writes:

Marc> Just a note that up to GDB 6.8, we used the output of "info threads"
Marc> in the DSF-GDB Eclipse frontend.  With GDB 7.0 we moved to
Marc> "-thread-info"
Marc> So, I'm not affected by a change of output

Unfortunately both -thread-info and "info threads" just amount to a
call to print_thread_info.  So, if we fix that to use a table, it will
change the MI output, IIUC.

FWIW, using a table in these situations seems superior to me, because
it allows for column headings and because it handles some of the
formatting bits (lining up columns) automatically.

So, at least IMO, code like this should prefer tables over things like
emitting sequences of spaces.  If I'm missing some obvious drawback
here, please let me know, since I'd like to be informed...q

Marc> I'm not sure if you enforce CLI output backwards compatibility...

I think we definitely should not.

Tom


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