This is the mail archive of the
mailing list for the GDB project.
GDB 5.2 or GDB 5.1.1?
- From: Andrew Cagney <ac131313 at redhat dot com>
- To: gdb at sources dot redhat dot com
- Date: Wed, 09 Jan 2002 16:57:12 -0500
- Subject: GDB 5.2 or GDB 5.1.1?
I'm looking over all the things in my 5.1.1 folder and am beginning to
think that it might be better if instead just move onto 5.2. I really
don't know if it is worth all the effort (well mine and a few others) of
pulling those changes onto a branch. All the C++ fixes, the HP/UX host
stuff and so on.
For this to work, all the proposed release criteria for 5.2 would need
to be droped.
Either way, there needs to be a decision by the middle of next week.
GDB 5.2 - Fixes
GDB 5.2 - New features
GCC 3.0 ABI support (but hopefully sooner...).
Objective C/C++ support (but hopefully sooner...).
Import of readline 4.2
GDB 5.2 - Cleanups
The following cleanups have been identified as part of GDB 5.2.
Remove old code that does not use ui_out functions and all the related
"ifdef"s. This also allows the elimination of -DUI_OUT from
Makefile.in and configure.in.
Eliminate warnings for all targets on at least one host for one of the
-W flags. Flags up for debate include: -Wswitch -Wcomment -trigraphs
-Wtrigraphs -Wunused-function -Wunused-label -Wunused-variable
-Wunused-value -Wchar-subscripts -Wtraditional -Wshadow -Wcast-qual
-Wcast-align -Wwrite-strings -Wconversion -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-declarations -Wredundant-decls
Deprecate, if not delete, the following:
Replaced by, on the target side
and on core-gdb side:
Remote.c will need to use something
other than REGISTER_BYTE() and
REGISTER_RAW_SIZE() when unpacking
Now handed by the methods
which sits between core GDB and
the register cache.
I think these three are redundant.
do any conversion it likes.
I think these can be replaced by
FRAME_REGISTER_INFO (frame, ...)
If nothing else rename this so that
how it relates to rawreg and the
regnum is clear.
The size of the cache can be computed
on the fly.
The pseudo registers should eventually make
Obsolete the targets:
Obsolete the protocols:
``As of version 5.3, WindRiver has removed the RDB server (RDB
protocol support is built into gdb).'' -- Till.
Restructure gdb directory tree so that it avoids any 8.3 and 14
Convert GDB build process to AUTOMAKE.
See also sub-directory configure below.
The current convention is (kind of) to use $(<header>_h) in all
dependency lists. It isn't done in a consistent way.