+-- 2001-03-08
+
+Update GDB's coding standard documentation. Known topics:
+
+ o alloca/malloc et.al.
+
+ o typedef and structs
+
+ o ISO-C
+
+and most likely also:
+
+ o include conventions
+
+--
+
+Wow, three bug reports for the same problem in one day! We should
+probably make fixing this a real priority :-).
+
+Anyway, thanks for reporting.
+
+The following patch will fix the problems with setting breakpoints in
+dynamically loaded objects:
+
+ http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00230.html
+
+This patch isn't checked in yet (ping Michael/JimB), but I hope this
+will be in the next GDB release.
+
+There should really be a test in the testsuite for this problem, since
+it keeps coming up :-(. Any volunteers?
+
+Mark
+
+--
+
+x86 linux GDB and SIGALRM (???)
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00803.html
+
+This problem has been fixed, but a regression test still needs to be
+added to the testsuite:
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00309.html
+
+Mark
+
+[The test has been submitted for approval - cagney]
+
+--
+
+RFD: infrun.c: No bpstat_stop_status call after proceed over break?
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00665.html
+
+GDB misses watchpoint triggers after proceeding over a breakpoint on
+x86 targets.
+
+--
+
+GDB 5.0 doesn't work on Linux/SPARC
+
+There are two parts to this.
+
+ o GDB 5.0 doesn't work on GNU/Linux/SPARC32
+
+ o GDB 5.0 doesn't work on the new target
+ GNU/Linux/SPARC64
+
+GDB does build on both these targets.
+
+The first problem is the one that should be fixed.
+
+--
+
+ GDB 5.1 - New features
+ ======================
+
+The following new features should be included in 5.1.
+
+--
+
+Enable MI by default. Old code can be deleted after 5.1 is out.
+
+Issues:
+
+ o syntax change where a list would
+ look like:
+ [ foo=a, foo=b, foo=c ]
+ instead of
+ { foo=a, foo=b, foo=c }
+
+ o kill off the idea of a reverse
+ query.
+
+ o review test cases
+
+ o enable it
+
+--
+
+Pascal (Pierre Muller, David Taylor)
+
+Pierre Muller has contributed patches for adding Pascal Language
+support to GDB.
+
+2 pascal language patches inserted in database
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00521.html
+
+Indent -gnu ?
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00496.html
+
+[I think this has been merged, need to confirm - cagney]
+
+--
+
+Java (Anthony Green, David Taylor)
+
+Anthony Green has a number of Java patches that did not make it into
+the 5.0 release. The first two are in cvs now, but the third needs
+some fixing up before it can go in.
+
+Patch: java tests
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00512.html
+
+Patch: java booleans
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00515.html
+
+Patch: handle N_MAIN stab
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00527.html
+
+-- 2001-03-08
+
+Add CRIS target.
+
+A predicate to this is the multi-arching of SOFTWARE_SINGLE_STEP(). A
+patch has been submitted.
+
+--
+
+ GDB 5.1 - Cleanups
+ ==================
+
+The following code cleanups will hopefully be applied to GDB 5.1.
+
+-- 2001-03-22
+
+Resolve the build status of all broken targets as identified by the
+MAINTAINERS file.
+
+ o arm-* vs NetBSD's lack of ``unix''
+ o arm-* vs IRIX (see below)
+
+ o delete m88k?
+
+ o delete mpw?
+
+-- 2001-03-15
+
+ Obsolete some targets.
+
+Possible selection criteria are:
+
+ o uses a deprecated feature
+
+ o doesn't build
+
+ o doesn't have a maintainer
+
+Steps:
+
+ o post proposals to gdb@ (DONE)
+
+ o post announcement to gdb-announce@
+ crossed with gdb@ reply-to to gdb@
+ (DONE)
+
+ ns32k-*-mach3*
+ ns32k-umax-*
+ ns32k-utek-sysv*
+ tic80-*
+ m68*-isi-*
+ m68*-sony-*
+ m68*-rom68k-*
+ m68*-*bug-*
+ m68*-monitor-*
+ m68*-est-*
+ a29k-ultra3
+ powerpcle-*-solaris*
+ powerpcle-*-cygwin*
+ powerpc-*-netware*
+ w65-*-*
+ i[3456]86-*-sunos*
+
+ o clobber the files:
+
+ configure.{in,host,tgt}
+ Makefile.in
+ *-tdep.c *-nat.c *-xdep.c
+ configure/*/*
+
+ o update NEWS
+
+--
+
+Change documentation to GFDL license.
+
+``It is time to make an effort to start using the GFDL more
+thoroughly. Would all GNU maintainers please change the license to
+the GFDL, for all manuals and other major documentation files?
+
+The GFDL and some instructions for using it can be found in
+http://www.gnu.org/copyleft/''
+
+ RMS
+
+--
+
+Fix copyright notices.
+
+Turns out that ``1998-2000'' isn't considered valid :-(
+
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00467.html
+
+--
+
+ GDB 5.1 - Known Problems
+ ========================
+
+--
+
+z8k
+
+The z8k has suffered bit rot and is known to not build. The problem
+was occuring in the opcodes directory.
+
+--
+
+Solaris 8 x86 CURSES_H problem
+http://sources.redhat.com/ml/gdb/2000-07/msg00038.html
+
+The original problem was worked around with:
+
+ 2000-06-06 Michael Snyder <msnyder@cygnus.com>
+
+ * configure.in: Enable autoconf to find curses.h on Solaris 2.8.
+ * configure: Regenerate.
+
+When building both GDB and SID using the same source tree the problem
+will still occure. sid/component/configure.in mis-configures
+<curses.h> and leaves wrong information in the config cache.
+
+--
+
+ GDB 5.2 - Fixes
+ ===============
+
+--
+
+Thread support. Right now, as soon as a thread finishes and exits,
+you're hosed. This problem is reported once a week or so.
+
+--
+
+ GDB 5.2 - New features
+ ======================
+
+--
+
+GCC 3.0 ABI support (but hopefully sooner...).
+
+--
+
+Objective C/C++ support (but hopefully sooner...).
+
+--
+
+ 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.
+
+--
+
+Compiler warnings.
+
+Eliminate all warnings for at least one host/target for the flags:
+-Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses
+-Wpointer-arith -Wuninitialized
+
+--
+
+Restructure gdb directory tree so that it avoids any 8.3 and 14
+filename problems.
+
+--
+
+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.
+
+--
+
+ GDB 5.2 - Known Problems
+ ========================
+
+--
+
+ Code Cleanups: General
+ ======================
+
+The following are more general cleanups and fixes. They are not tied
+to any specific release.
+
+--
+
+Rename read_register{,_pid}() to read_unsigned_register{,_pid}().
+
+--
+
+Can't build IRIX -> arm GDB.
+http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00356.html
+
+David Whedon writes:
+> Now I'm building for an embedded arm target. If there is a way of turning
+> remote-rdi off, I couldn't find it. It looks like it gets built by default
+> in gdb/configure.tgt(line 58) Anyway, the build dies in
+> gdb/rdi-share/unixcomm.c. SERPORT1 et. al. never get defined because we
+> aren't one of the architectures supported.
+
+--
+
+Problem with weak functions
+http://sourceware.cygnus.com/ml/gdb/2000-05/msg00060.html
+
+Dan Nicolaescu writes:
+> It seems that gdb-4.95.1 does not display correctly the function when
+> stoping in weak functions.
+>
+> It stops in a function that is defined as weak, not in the function
+> that is actually run...
+
+--
+
+Follow through `make check' with --enable-shared.
+
+When the srcware tree is configured with --enable-shared, the `expect'
+program won't run properly. Jim Wilson found out gdb has a local hack
+to set LD_LIBRARY_PATH, but, AFAIK, no other project has been hacked
+similarly.
+
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00845.html
+
+--
+
+Delete macro TARGET_BYTE_ORDER_SELECTABLE.
+
+Patches in the database.
+
+--
+
+printcmd.c (print_address_numeric):
+
+NOTE: This assumes that the significant address information is kept in
+the least significant bits of ADDR - the upper bits were either zero
+or sign extended. Should ADDRESS_TO_POINTER() or some
+ADDRESS_TO_PRINTABLE() be used to do the conversion?
+
+--
+
+The BFD directory requires bug-fixed AUTOMAKE et.al.
+
+AUTOMAKE 1.4 incorrectly set the TEXINPUTS environment variable. It
+contained the full path to texinfo.tex when it should have only
+contained the directory. The bug has been fixed in the current
+AUTOMAKE sources. Automake snapshots can be found in:
+ ftp://sourceware.cygnus.com/pub/gdb/snapshots
+and ftp://sourceware.cygnus.com/pub/binutils
+
+--
+
+Find something better than DEFAULT_BFD_ARCH, DEFAULT_BFD_VEC to
+determine the default isa/byte-order.
+
+--
+
+Rely on BFD_BIG_ENDIAN and BFD_LITTLE_ENDIAN instead of host dependent
+BIG_ENDIAN and LITTLE_ENDIAN.
+
+--
+
+Eliminate more compiler warnings.
+
+Of course there also needs to be the usual debate over which warnings
+are valid and how to best go about this.
+
+One method: choose a single option; get agreement that it is
+reasonable; try it out to see if there isn't anything silly about it
+(-Wunused-parameters is an example of that) then incrementally hack
+away.
+
+The other method is to enable all warnings and eliminate them from one
+file at a time.
+
+--
+
+Elimination of ``(catch_errors_ftype *) func''.
+
+Like make_cleanup_func it isn't portable.
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00791.html
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00814.html
+
+--
+
+Nuke #define CONST_PTR.
+
+--
+
+Nuke USG define.
+
+--
+
+[PATCH/5] src/intl/Makefile.in:distclean additions
+http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00363.html
+
+Do not forget to merge the patch back into the trunk.
+
+--
+
+Rationalize the host-endian code (grep for HOST_BYTE_ORDER).
+
+At present defs.h includes <endian.h> (which is linux specific) yet
+almost nothing depends on it. Suggest "gdb_endian.h" which can also
+handle <machine/endian.h> and only include that where it is really
+needed.
+
+--
+
+Replace savestring() with something from libiberty.
+
+An xstrldup()? but that would have different semantics.
+
+--
+
+Rationalize use of floatformat_unknown in GDB sources.
+
+Instead of defaulting to floatformat_unknown, should hosts/targets
+specify the value explicitly?
+
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00447.html
+
+--
+
+Add a ``name'' member to include/floatformat.h:struct floatformat.
+Print that name in gdbarch.c.
+
+--
+
+Sort out the harris mess in include/floatformat.h (it hardwires two
+different floating point formats).
+
+--
+
+See of the GDB local floatformat_do_doublest() and libiberty's
+floatformat_to_double (which was once GDB's ...) can be merged some
+how.
+
+--
+
+Eliminate mmalloc(), mstrsave() et.al. from GDB.
+
+Also eliminate it from defs.h.
+
+--
+
+Eliminate PTR. ISO-C allows ``void *''.
+
+--
+
+Eliminate abort ().
+
+GDB should never abort. GDB should either throw ``error ()'' or
+``internal_error ()''. Better still GDB should naturally unwind with
+an error status.
+
+--
+
+GDB probably doesn't build on FreeBSD pre 2.2.x
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00378.html
+
+Fixes to get FreeBSD working on 2.2.x, 3.x and 4.x caused the code to
+suffer bit rot.
+
+--
+
+Deprecate "fg". Apparently ``fg'' is actually continue.
+
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00417.html
+
+--
+
+Deprecate current use of ``floatformat_unknown''.
+
+Require all targets to explicitly provide their float format instead
+of defaulting to floatformat unknown. Doing the latter leads to nasty
+bugs.
+
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00447.html
+
+--
+
+Rationalize floatformat_to_double() vs floatformat_to_doublest().
+
+Looks like GDB migrated floatformat_to_double() to libiberty but then
+turned around and created a ..._to_doublest() the latter containing
+several bug fixes.
+
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00472.html
+
+--
+
+Move floatformat_ia64_ext to libiberty/include floatformat.[ch].
+
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00466.html
+
+--
+
+The ``maintenance deprecate set endian big'' command doesn't notice
+that it is deprecating ``set endian'' and not ``set endian big'' (big
+is implemented using an enum). Is anyone going to notice this?
+
+--
+
+When tab expanding something like ``set arch<tab>'' ignore the
+deprecated ``set archdebug'' and expand to ``set architecture''.
+
+--
+
+Eliminate ``arm_register_names[j] = (char *) regnames[j]'' and the
+like from arm-tdep.c.
+
+--
+
+Fix uses of ->function.cfunc = set_function().
+
+The command.c code calls sfunc() when a set command. Rather than
+change it suggest fixing the callback function so that it is more
+useful. See:
+
+http://sourceware.cygnus.com/ml/gdb-patches/2000-06/msg00062.html
+
+See also ``Fix implementation of ``target xxx''.'' below.
+
+--
+
+IRIX 3.x support is probably broken.
+
+--
+
+Delete sim/SIM_HAVE_BREAKPOINTS and gdb/SIM_HAS_BREAKPOINTS.
+http://sourceware.cygnus.com/ml/gdb-patches/2000-07/msg00042.html
+
+Apart from the d30v, are there any sim/common simulators that make use
+of this?
+
+A brief summary of what happened is that sim/common/sim-break.c was
+created as a good idea. It turned out a better idea was to use
+SIM_SIGBREAK and have GDB pass back sim_resume (..., SIGBREAK).
+
+--
+
+Move remote_remove_hw_breakpoint, remote_insert_hw_breakpoint,
+remote_remove_watchpoint, remote_insert_watchpoint into target vector.
+
+--
+
+Eliminate ``extern'' from C files.
+
+--
+
+Replace ``STREQ()'' et.al. with ``strcmp() == 0'' et.al.
+
+Extreme care is recommeded - perhaps only modify tests that are
+exercised by the testsuite (as determined using some type of code
+coverage analysis).
+
+--
+
+Replace the file gdb/CONTRIBUTE with a file that is generated from the
+gdb/doc/*.texinfo directory.
+
+--
+
+ New Features and Fixes
+ ======================
+
+These are harder than cleanups but easier than work involving
+fundamental architectural change.
+
+--
+
+Hardware watchpoint problems on x86 OSes, including Linux:
+
+1. Delete/disable hardware watchpoints should free hardware debug
+registers.
+2. Watch for different values on a viariable with one hardware debug
+register.
+
+According to Eli Zaretskii <eliz@delorie.com>:
+
+These are not GDB/ia32 issues per se: the above features are all
+implemented in the DJGPP port of GDB and work in v5.0. Every
+x86-based target should be able to lift the relevant parts of
+go32-nat.c and use them almost verbatim. You get debug register
+sharing through reference counts, and the ability to watch large
+regions (up to 16 bytes) using multiple registers. (The required
+infrastructure in high-level GDB application code, mostly in
+breakpoint.c, is also working since v5.0.)
+
+--
+
+Add built-by, build-date, tm, xm, nm and anything else into gdb binary
+so that you can see how the GDB was created.
+
+--
+
+Add an "info bfd" command that displays supported object formats,
+similarly to objdump -i.
+
+Is there a command already?
+
+--
+
+Fix ``I'm sorry, Dave, I can't do that.'' from symfile.c.
+
+This requires internationalization.
+
+--
+
+Add support for:
+
+(gdb) p fwprintf(stdout,L"%S\n", f)
+No symbol "L" in current context.
+
+--
+
+Cleanup configury support for optional sub-directories.
+
+Check how GCC handles multiple front ends for an example of how things
+could work. A tentative first step is to rationalize things so that
+all sub directories are handled in a fashion similar to gdb/mi.
+
+See also automake above.
+
+--
+
+Add a transcript mechanism to GDB.
+
+Such a mechanism might log all gdb input and output to a file in a
+form that would allow it to be replayed. It could involve ``gdb
+--transcript=FILE'' or it could involve ``(gdb) transcript file''.
+
+--
+
+Can the xdep files be replaced by autoconf?
+
+--
+
+Document trace machinery
+
+--
+
+Document ui-out and ui-file.
+
+http://sourceware.cygnus.com/ml/gdb/2000-04/msg00121.html
+
+--
+
+Update texinfo.tex to latest?
+
+--
+
+Incorporate agentexpr.texi into gdb.texinfo
+
+agentexpr.texi mostly describes the details of the byte code used for
+tracepoints, not the internals of the support for this in GDB. So it
+looks like gdb.texinfo is a better place for this information.
+
+http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00566.html
+
+--
+
+Document overlay machinery.
+
+--
+
+``(gdb) catch signal SIGNAL''
+
+Overlaps with ``handle SIGNAL'' but the implied behavior is different.
+You can attach commands to a catch but not a handle. A handle has a
+limited number of hardwired actions.
+
+--
+
+Fix TUI
+
+ o readline/*.h bitrot
+
+ The TUI isn't up-to-date with
+ respect to the readline currently
+ bundled with GDB. Importing a
+ new readline is on the 5.1 wish
+ list so this can only get worse.
+
+ Grep for things like term_cursor_move.
+
+ (To be honest, I don't see anyone
+ importing a new readline before 5.1 is
+ out)
+
+ o tui.c:va_catch_errors() bitrot
+
+ This nasty piece of work used knowledge
+ of the internals of GDBs error functions :-(
+ Ever since those internals were cleaned
+ up this code has been broken. :-(
+
+ o tuiWin.c:c_makeVisibleWithNewHeight() broken
+ tuiLayout.c:_extractDisplayStartAddr() broken
+
+ Both these function call find_line_pc()
+ incorrectly (wrong args, wrong return value).
+
+ I suspect this bug has always been there!
+ It had been hidden because those files
+ didn't include the necessary header files
+ from gdb proper :-(
+
+ o tuiRegs() host dependant
+
+ Not suprisingly, this isn't a very portable
+ section of code. However, I'm sure people
+ could live with no regs in the short to
+ medium term.
+
+ o defs.h: #include "tui.h" et.al.
+
+ I'm not sure where this came from.
+ It was a really bad idea.
+
+ To get things to compile I did a nasty
+ hack (Just declare what was needed and
+ replace any expressions like xx->y.z()
+ in GDB proper with function calls). I
+ could commit it slightly cleaned up if
+ you like.
+
+ Medium Term. the #ifdef TUI and TuiDo()
+ should be changed to hooks (like GDBTK).
+ The gdb-events.[hc] is there for that
+ purpose (1)
+
+ o tui.c:_tuiReset() host dependant
+
+ tui.c contains a lump of termio[s]
+ I suspect an equivalent block of
+ code can be lifted from readline.
+ An equivalent readline function may
+ even be available.
+
+ o curses.h vs ncurses.h.
+
+ Simple portability problem.
+
+ o subsetCompare()
+
+ This function is a mystery - where is it?
+
+ o tui-file.[hc] cleanup
+
+ This can be significantly simplified.
+
+ o The code should be pacified. (-Werror -W...)
+
+ There are plenty of #includes,
+ duplicate #includes, missing function decls
+ and the like.
+
+ Some of the problems I found were through
+ fixing a few of the warnings.
+
+ o The code should be GNUtified.
+
+ It would be very nice to have this code
+ look like the rest of GDB. That way people
+ would be more accepting of it as a true
+ gdb component.
+
+ Until it is GNUtified it is going to stick
+ out like a sore thumb to the programmer.
+
+ o The code should be clearly copyrighted
+
+ (FSF, with due credit to HP)
+
+--
+
+Add support for ``gdb --- PROGRAM ARGS ...''.
+Add support for ``gdb -cmd=...''
+
+Along with many variations. Check:
+
+????? for a full discussion.
+
+for a discussion.
+
+--
+
+Implement ``(gdb) !ls''.
+
+Which is very different from ``(gdb) ! ls''. Implementing the latter
+is trivial.
+
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00034.html
+
+--
+
+Change the (char *list[]) to (const char (*)[]) so that dynamic lists can
+be passed.
+
+--
+
+When tab expanding something like ``set arch<tab>'' ignore the
+deprecated ``set archdebug'' and expand to ``set architecture''.
+
+--
+
+Replace the code that uses the host FPU with an emulator of the target
+FPU.
+
+--
+
+The "ocd reset" command needs to flush the dcache, which requires breaking
+the abstraction layer between the target independent and target code. One
+way to address this is provide a generic "reset" command and target vector.
+
+http://sources.redhat.com/ml/gdb-patches/2000-10/msg00011.html
+
+--
+
+ Thread Support
+ ==============
+
+--
+
+Generic: lin-thread cannot handle thread exit (Mark Kettenis, Michael
+Snyder) http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00525.html
+
+The thread_db assisted debugging code doesn't handle exiting threads
+properly, at least in combination with glibc 2.1.3 (the framework is
+there, just not the actual code). There are at least two problems
+that prevent this from working.
+
+As an additional reference point, the pre thread_db code did not work
+either.
+
+--
+
+GNU/Linux/x86 and random thread signals (and Solaris/SPARC but not
+Solaris/x86).
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00336.html
+
+Christopher Blizzard writes:
+
+So, I've done some more digging into this and it looks like Jim
+Kingdon has reported this problem in the past:
+
+http://sourceware.cygnus.com/ml/bug-gdb/1999-10/msg00058.html
+
+I can reproduce this problem both with and without Tom's patch. Has
+anyone seen this before? Maybe have a solution for it hanging around?
+:)
+
+There's a test case for this documented at:
+
+when debugging threaded applications you get extra SIGTRAPs
+http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=9565
+
+[There should be a GDB testcase - cagney]
+
+--
+
+GDB5 TOT on unixware 7
+http://sourceware.cygnus.com/ml/gdb/2000-04/msg00119.html
+
+Robert Lipe writes:
+> I just spun the top of tree of the GDB5 branch on UnixWare 7. As a
+> practical matter, the current thread support is somewhat more annoying
+> than when GDB was thread-unaware.
+
+--
+
+ Language Support
+ ================
+
+New languages come onto the scene all the time.
+
+--
+
+Re: Various C++ things
+
+value_headof/value_from_vtable_info are worthless, and should be
+removed. The one place in printcmd.c that uses it should use the RTTI
+functions.
+
+RTTI for g++ should be using the typeinfo functions rather than the
+vtables. The typeinfo functions are always at offset 4 from the
+beginning of the vtable, and are always right. The vtables will have
+weird names like E::VB sometimes. The typeinfo function will always
+be "E type_info function", or somesuch.
+
+value_virtual_fn_field needs to be fixed so there are no failures for
+virtual functions for C++ using g++.
+
+Testsuite cases are the major priority right now for C++ support,
+since i have to make a lot of changes that could potentially break
+each other.
+
+--
+
+Add support for Modula3
+
+Get DEC/Compaq to contribute their Modula-3 support.
+
+--
+
+ Remote Protocol Support
+ =======================
+
+--
+
+Revised UDP support (was: Re: [Fwd: [patch] UDP transport support])
+http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00000.html
+
+(Broken) support for GDB's remote protocol across UDP is to be
+included in the follow-on release.
+
+It should be noted that UDP can only work when the [Gg] packet fits in
+a single UDP packet.
+
+There is also much debate over the merit of this.
+
+--
+
+Migrate qfThreadInfo packet -> qThreadInfo. (Andrew Cagney)
+
+Add support for packet enable/disable commands with these thread
+packets. General cleanup.
+
+[PATCH] Document the ThreadInfo remote protocol queries
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00832.html
+
+[PATCH] "info threads" queries for remote.c
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00831.html
+
+--
+
+Remote protocol doco feedback.
+
+Too much feedback to mention needs to be merged in (901660). Search
+for the word ``remote''.
+
+
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00023.html
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00056.html
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00382.html
+
+--
+
+GDB doesn't recover gracefully from remote protocol errors.
+
+GDB wasn't checking for NAKs from the remote target. Instead a NAK is
+ignored and a timeout is required before GDB retries. A pre-cursor to
+fixing this this is making GDB's remote protocol packet more robust.
+
+While downloading to a remote protocol target, gdb ignores packet
+errors in so far as it will continue to download with chunk N+1 even
+if chunk N was not correctly sent. This causes gdb.base/remote.exp to
+take a painfully long time to run. As a PS that test needs to be
+fixed so that it builds on 16 bit machines.
+
+--
+
+Fix the ``!'' packet.
+
+JT reported that the existing targets do, in fact return ``OK'' so it
+is possible to merge remote and extended-remote targets.
+
+--
+
+Drop ``<address>'' from the [SsCc] packets.
+
+I don't think that GDB generates them so having it in the protocol is
+silly.
+
+--
+
+Fix doco on the ``q'' packet.
+
+It has evolved into a generic RPC. The notes should reflect this and,
+perhaps, the ``Q'' packet can be deprecated.
+
+The doco should mention that ``OK'' is a valid packet response.
+
+The doco should explain why ``OK'' needs to be a valid packet
+response.
+
+--
+
+Add the cycle step command.
+
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00237.html
+
+--
+
+Resolve how to scale things to support very large packets.
+
+--
+
+Resolve how to handle a target that changes things like its endianess
+on the fly - should it be returned in the ``T'' packet?
+
+Underlying problem is that the register file is target endian. If the
+target endianess changes gdb doesn't know.
+
+--
+
+ Symbol Support
+ ==============
+
+If / when GDB starts to support the debugging of multi-processor
+(rather than multi-thread) applications the symtab code will need to
+be updated a little so that several independent symbol tables are
+active at a given time.
+
+The other interesting change is a clarification of the exact meaning
+of CORE_ADDR and that has had consequences for a few targets (that
+were abusing that data type).
+
+--
+
+Investiagate ways of reducing memory.
+
+--
+
+Investigate ways of improving load time.
+
+--
+
+Get the d10v to use POINTER_TO_ADDRESS and ADDRESS_TO_POINTER.
+
+Consequence of recent symtab clarification. No marks for figuring out
+who maintains the d10v.
+
+--
+
+Get the MIPS to correctly sign extend all address <-> pointer
+conversions.
+
+Consequence of recent symtab clarification. No marks for figuring out
+who maintains the MIPS.
+
+--
+
+GDB truncates 64 bit enums.
+
+http://sourceware.cygnus.com/ml/gdb-patches/2000-06/msg00290.html
+
+--
+
+ Testsuite Support
+ =================
+
+There are never to many testcases.
+
+--
+
+Better thread testsuite.
+
+--
+
+Better C++ testsuite.
+
+--
+
+Look at adding a GDB specific testsuite directory so that white box
+tests of key internals can be added (eg ui_file).
+
+--
+
+Separate out tests that involve the floating point (FP).
+
+(Something for people brining up new targets). FP and non-fp tests
+are combined. I think there should be set of basic tests that
+exercise pure integer support and then a more expanded set that
+exercise FP and FP/integer interactions.
+
+As an example, the MIPS, for n32 as problems with passing FP's and
+structs. Since most inferior call tests include FP it is difficult to
+determine of the integer tests are ok.
+
+--
+
+ Architectural Changes: General
+ ==============================
+
+These are harder than simple cleanups / fixes and, consequently
+involve more work. Typically an Architectural Change will be broken
+down into a more digestible set of cleanups and fixes.
+
+--
+
+Cleanup software single step.
+
+At present many targets implement software single step by directly
+blatting memory (see rs6000-tdep.c). Those targets should register
+the applicable breakpoints using the breakpoint framework. Perhaphs a
+new internal breakpoint class ``step'' is needed.
+
+--
+
+Replace READ_FP() with FRAME_HANDLE().
+
+READ_FP() is a hangover from the days of the vax when the ABI really
+did have a frame pointer register. Modern architectures typically
+construct a virtual frame-handle from the stack pointer and various
+other bits of string.
+
+Unfortunately GDB still treats this synthetic FP register as though it
+is real. That in turn really confuses users (arm and ``print $fp'' VS
+``info registers fp''). The synthetic FP should be separated out of
+the true register set presented to the user.
+
+--
+
+Register Cache Cleanup (below from Andrew Cagney)
+
+I would depict the current register architecture as something like:
+
+ High GDB --> Low GDB
+ | |
+ \|/ \|/
+ --- REG NR -----
+ |
+ register + REGISTER_BYTE(reg_nr)
+ |
+ \|/
+ -------------------------
+ | extern register[] |
+ -------------------------
+
+where neither the high (valops.c et.al.) or low gdb (*-tdep.c) are
+really clear on what mechanisms they should be using to manipulate that
+buffer. Further, much code assumes, dangerously, that registers are
+contigious. Having got mips-tdep.c to support multiple ABIs, believe
+me, that is a bad assumption. Finally, that register cache layout is
+determined by the current remote/local target and _not_ the less
+specific target ISA. In fact, in many cases it is determined by the
+somewhat arbitrary layout of the [gG] packets!
+
+
+How I would like the register file to work is more like:
+
+
+ High GDB
+ |
+ \|/
+ pseudo reg-nr
+ |
+ map pseudo <->
+ random cache
+ bytes
+ |
+ \|/
+ ------------
+ | register |
+ | cache |
+ ------------
+ /|\
+ |
+ map random cache
+ bytes to target
+ dependent i-face
+ /|\
+ |
+ target dependent
+ such as [gG] packet
+ or ptrace buffer
+
+The main objectives being:
+
+ o a clear separation between the low
+ level target and the high level GDB
+
+ o a mechanism that solves the general
+ problem of register aliases, overlaps
+ etc instead of treating them as optional
+ extras that can be wedged in as an after
+ thought (that is a reasonable description
+ of the current code).
+
+ Identify then solve the hard case and the
+ rest just falls out. GDB solved the easy
+ case and then tried to ignore the real
+ world :-)
+
+ o a removal of the assumption that the
+ mapping between the register cache
+ and virtual registers is largely static.
+ If you flip the USR/SSR stack register
+ select bit in the status-register then
+ the corresponding stack registers should
+ reflect the change.
+
+ o a mechanism that clearly separates the
+ gdb internal register cache from any
+ target (not architecture) dependent
+ specifics such as [gG] packets.
+
+Of course, like anything, it sounds good in theory. In reality, it
+would have to contend with many<->many relationships at both the
+virt<->cache and cache<->target level. For instance:
+
+ virt<->cache
+ Modifying an mmx register may involve
+ scattering values across both FP and
+ mmpx specific parts of a buffer
+
+ cache<->target
+ When writing back a SP it may need to
+ both be written to both SP and USP.
+
+
+Hmm,
+
+Rather than let this like the last time it was discussed, just slip, I'm
+first going to add this e-mail (+ references) to TODO. I'd then like to
+sketch out a broad strategy I think could get us there.
+
+
+First thing I'd suggest is separating out the ``extern registers[]''
+code so that we can at least identify what is using it. At present
+things are scattered across many files. That way we can at least
+pretend that there is a cache instead of a global array :-)
+
+I'd then suggest someone putting up a proposal for the pseudo-reg /
+high-level side interface so that code can be adopted to it. For old
+code, initially a blanket rename of write_register_bytes() to
+deprecated_write_register_bytes() would help.
+
+Following that would, finaly be the corresponding changes to the target.
+
+--
+
+Check that GDB can handle all BFD architectures (Andrew Cagney)
+
+There should be a test that checks that BFD/GDB are in sync with
+regard to architecture changes. Something like a test that first
+queries GDB for all supported architectures and then feeds each back
+to GDB.. Anyone interested in learning how to write tests? :-)
+
+--
+
+ Architectural Change: Multi-arch et al.
+ =======================================
+
+The long term objective is to remove all assumptions that there is a
+single target with a single address space with a single instruction
+set architecture and single application binary interface.
+
+This is an ongoing effort. The first milestone is to enable
+``multi-arch'' where by all architectural decisions are made at
+runtime.
+
+It should be noted that ``gdbarch'' is really ``gdbabi'' and
+``gdbisa''. Once things are multi-arched breaking that down correctly
+will become much easier.