This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: New ARI web page, generated using script inside CVS tree in gdb/contrib/ari directory
- From: Tom Tromey <tromey at redhat dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>, gdb at sourceware dot org
- Date: Wed, 14 Nov 2012 09:40:59 -0700
- Subject: Re: New ARI web page, generated using script inside CVS tree in gdb/contrib/ari directory
- References: <002701cdc0b9$542d2560$fc877020$@muller@ics-cnrs.unistra.fr> <20121112180707.GQ4847@adacore.com>
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> But perhaps we should also look at possibly importing gnulib's stat
Joel> and sys_wait modules? Not a trivial change in the sense that it could
Joel> be not equivalent to what we have now, and thus have unintended
Joel> consequences; but perhaps worth a shot. I think that gdb_stat.h and
Joel> all other such headers were GDB's own way of doing what gnulib does
Joel> in general.
FWIW I tend to favor more use of gnulib in gdb. In general I think the
pros outweigh the cons; especially since it seems reasonably easy to get
fixes into gnulib, and because importing a new gnulib snapshot is also
simple.
The pros seem to be -- shared development, good documentation, and
letting the main gdb source use standard headers and standard functions.
I think the primary con is that a gnulib module may have a bug, and then
we have to fix it elsewhere first. This doesn't seem to be a major
problem.
Tom