find out whether anyone else is working on it.
- Known problems in GDB 5.0
- =========================
+ GDB 5.1 - Fixes
+ ===============
Below is a list of problems identified during the GDB 5.0 release
-cycle. People hope to have these problems fixed in a follow-on
-release.
+cycle. People hope to have these problems fixed in 5.1.
-(The names in paren indicate people that posted the original problem.)
+-- 2001-03-08
---
+Update GDB's coding standard documentation. Known topics:
+
+ o alloca/malloc et.al.
-GDB requires GCC to build under IRIX
+ o typedef and structs
-IRIX, being more pedantic than GCC reports as errors certain
-assignments that GCC treats as warnings.
+ o ISO-C
-This can be worked around by building GDB with the GCC compiler.
+and most likely also:
+
+ o include conventions
--
-The BFD directory requires bug-fixed AUTOMAKE et.al.
+Obsolete ser-ocd.c.
-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
+--
+
+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
--
-Possible regressions with some devel GCCs.
-http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00475.html
+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
-gcc-2.95.2 outputs a line note *before* the prologue (and one for the
-closing brace after the epilogue, instead of before it, as it used to
-be). By disabling the RTL-style prologue generating mechanism
-(undocumented GCC option -mno-schedule-prologue), you get back the
-traditional behaviour.
-http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00510.html
+Mark
-This should now be fixed.
+[The test has been submitted for approval - cagney]
--
RFD: infrun.c: No bpstat_stop_status call after proceed over break?
-(Peter Schauer)
http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00665.html
GDB misses watchpoint triggers after proceeding over a breakpoint on
--
-x86 linux GDB and SIGALRM (???)
-http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00803.html
+GDB 5.0 doesn't work on Linux/SPARC
-I know there are problems with single stepping through signal
-handlers. These problems were present in 4.18. They were just masked
-because 4.18 failed to recognize signal handlers. Fixing it is not
-easy, and will require changes to handle_inferior_event(), that I
-prefer not to make before the 5.0 release.
+There are two parts to this.
-Mark
+ 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.
--
-Revised UDP support (was: Re: [Fwd: [patch] UDP transport support])
-http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00000.html
+ GDB 5.1 - New features
+ ======================
-(Broken) support for GDB's remote protocol across UDP is to be
-included in the follow-on release.
+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-26
+
+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)
+
+--
+
+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.
+
+--
+
+m88k
+
+The m88k has suffered bit rot and is known to not build.
+
+--
+
+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 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
+-Woverloaded-virtual -Winline
+
+--
+
+Deprecate, if not delete, the following:
+
+ register[]
+ register_valid[]
+ register_buffer()
+ REGISTER_BYTE()
+ Replaced by, on the target side
+ supply_register()
+ and on core-gdb side:
+ {read,write}_register_gen()
+ Remote.c will need to use something
+ other than REGISTER_BYTE() and
+ REGISTER_RAW_SIZE() when unpacking
+ [gG] packets.
+
+ STORE_PSEUDO_REGISTER
+ FETCH_PSEUDO_REGISTER
+ Now handed by the methods
+ gdbarch_{read,write}_register()
+ which sits between core GDB and
+ the register cache.
+
+ REGISTER_CONVERTIBLE
+ REGISTER_CONVERT_TO_RAW
+ REGISTER_CONVERT_TO_VIRTUAL
+ I think these three are redundant.
+ gdbarch_register_{read,write} can
+ do any conversion it likes.
+
+ REGISTER_VIRTUAL_SIZE
+ MAX_REGISTER_VIRTUAL_SIZE
+ REGISTER_VIRTUAL_TYPE
+ I think these can be replaced by
+ the pair:
+ FRAME_REGISTER_TYPE(frame, regnum)
+ REGISTER_TYPE(regnum)
+
+ DO_REGISTERS_INFO
+ Replace with
+ FRAME_REGISTER_INFO (frame, ...)
+
+ REGISTER_SIM_REGNO()
+ If nothing else rename this so that
+ how it relates to rawreg and the
+ regnum is clear.
+
+ REGISTER_BYTES
+ The size of the cache can be computed
+ on the fly.
+
+ IS_TRAPPED_INTERNALVAR
+ The pseudo registers should eventually make
+ this redundant.
+
+--
+
+Obsolete the targets.
+
+arm*-wince-pe
+mips*-*-pe
+sh*-*-pe
+
+Obsolete the protocols:
+
+RDB
+
+``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
+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.
+
+--
+
+Investigate changing --target=a29k-amd-udi to a29k-*-coff* and
+rationalize *.mt files. The got-ya is in remote-eb.c - it has its own
+custom tty manipulation - it should be using the serial object.
+
+--
+
+Rename read_register{,_pid}() to read_unsigned_register{,_pid}().
--
> stoping in weak functions.
>
> It stops in a function that is defined as weak, not in the function
-> that is actualy run...
+> that is actually run...
--
- Code Cleanups: Next Release
- ===========================
+Follow through `make check' with --enable-shared.
-The following are small cleanups that will hopefully be completed by
-the follow on to 5.0.
+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
--
--
-Purge PARAMS
-
-Eliminate all uses of PARAMS in GDB's source code.
-
---
+printcmd.c (print_address_numeric):
-Elimination of make_cleanup_func. (Andrew Cagney)
-
-make_cleanup_func elimination
-http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00791.html
-http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00814.html
+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?
--
-Fix copyright notices.
-
-Turns out that ``1998-2000'' isn't considered valid :-(
+The BFD directory requires bug-fixed AUTOMAKE et.al.
-http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00467.html
+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
--
- Code Cleanups: General
- ======================
-
-The following are more general cleanups and fixes. They are not tied
-to any specific release.
+Find something better than DEFAULT_BFD_ARCH, DEFAULT_BFD_VEC to
+determine the default isa/byte-order.
--
-ATTRIBUTE_UNUSED
-
-The need for this as almost been eliminated. The next version of GCC
-(assuming cagney gets the relevant patch committed) will be able to
-supress unused parameter warnings.
+Rely on BFD_BIG_ENDIAN and BFD_LITTLE_ENDIAN instead of host dependent
+BIG_ENDIAN and LITTLE_ENDIAN.
--
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.
--
--
-Replace asprintf() calls with xasprintf() calls.
-
-As with things like strdup() most calls to asprintf() don't check the
-return value.
-
---
-
-Replace strsave() + mstrsave() with libiberty:xstrdup().
-
---
-
Replace savestring() with something from libiberty.
An xstrldup()? but that would have different semantics.
--
-Eliminate mmalloc() from GDB.
+Eliminate mmalloc(), mstrsave() et.al. from GDB.
Also eliminate it from defs.h.
--
-Updated readline
-
-Readline 4.? is out. A merge wouldn't hurt. Patches are in:
-
-http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00436.html
-
---
-
Deprecate "fg". Apparently ``fg'' is actually continue.
http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00417.html
--
-Always build ser-tcp.c.
+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 patch as submitted was just going to add ser-tcp.c to the Alpha's
-makefile. A better patch is to instead add ser-tcp.c to SER_HARDWARE
-and make it a standard part of all debuggers.
+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:
-If problems occure then configure.in can sort them out.
+http://sourceware.cygnus.com/ml/gdb-patches/2000-06/msg00062.html
-http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00544.html
+See also ``Fix implementation of ``target xxx''.'' below.
--
-Follow through `make check' with --enable-shared.
+IRIX 3.x support is probably broken.
-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 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.
--
+Rewrite/break up sparcl-tdep.c so that it uses ser*.c as the mechanism
+for accessing either the serial or UDP port.
+
+--
New Features and Fixes
======================
--
+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.
-Some of these (*m.h) would be added to the generated config.h. That
-in turn would fix a long standing bug where by the build process many
-not notice a changed tm.h file. Since everything depends on config.h,
-a change to *m.h forces a change to config.h and, consequently forces
-a rebuild.
-
--
Add an "info bfd" command that displays supported object formats,
--
-Convert GDB build process to AUTOMAKE.
-
-See also sub-directory configure below.
+Add support for:
+
+(gdb) p fwprintf(stdout,L"%S\n", f)
+No symbol "L" in current context.
--
--
-Restructure gdb directory tree so that it avoids any 8.3 and 14
-filename problems.
-
---
-
Add a transcript mechanism to GDB.
Such a mechanism might log all gdb input and output to a file in a
Update texinfo.tex to latest?
-
-
--
Incorporate agentexpr.texi into gdb.texinfo
``(gdb) catch signal SIGNAL''
-Overlaps with ``handle SIGNAL'' but the implied behavour is different.
+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.
--
-Get the TUI working on all platforms.
+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)
--
--
+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
> practical matter, the current thread support is somewhat more annoying
> than when GDB was thread-unaware.
---
-
-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
-
--
Language Support
--
-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
-
---
-
-Java (Anthony Green, David Taylor)
+Re: Various C++ things
-Anthony Green has a number of Java patches that did not make it into
-the 5.0 release.
+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.
-Patch: java tests
-http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00512.html
+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.
-Patch: java booleans
-http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00515.html
+value_virtual_fn_field needs to be fixed so there are no failures for
+virtual functions for C++ using g++.
-Patch: handle N_MAIN stab
-http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00527.html
+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.
--
-[Comming...]
+Add support for Modula3
-Modify gdb to work correctly with Pascal.
+Get DEC/Compaq to contribute their Modula-3 support.
--
-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.
+ Remote Protocol Support
+ =======================
-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.
+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.
-Add support for Modula3
+It should be noted that UDP can only work when the [Gg] packet fits in
+a single UDP packet.
-Get DEC/Compaq to contribute their Modula-3 support.
+There is also much debate over the merit of this.
--
- Remote Protocol Support
- =======================
+Migrate qfThreadInfo packet -> qThreadInfo. (Andrew Cagney)
---
+Add support for packet enable/disable commands with these thread
+packets. General cleanup.
-set/show remote X-packet ...
+[PATCH] Document the ThreadInfo remote protocol queries
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00832.html
-``(gdb) help set remote X-packet'' doesn't list the applicable
-responses. The help message needs to be expanded.
+[PATCH] "info threads" queries for remote.c
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00831.html
--
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 edownload with chunk N+1 even
+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.
+
+Suggest encoding registers as NN!VALUE.
+
+--
+
+GDB should allow incomming packets to be larger than outgoing ones. A
+fully loaded T packet (containing all registers) can be very large -
+definitly larger than a corresponding Gg packet.
+
--
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 independant symbol tables are
+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
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
construct a virtual frame-handle from the stack pointer and various
other bits of string.
-Unfortunatly GDB still treats this synthetic FP register as though it
+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.
|
map random cache
bytes to target
- dependant i-face
+ dependent i-face
/|\
|
- target dependant
+ target dependent
such as [gG] packet
or ptrace buffer
o a mechanism that clearly separates the
gdb internal register cache from any
- target (not architecture) dependant
+ target (not architecture) dependent
specifics such as [gG] packets.
Of course, like anything, it sounds good in theory. In reality, it
--
-Fix ``set architecture <tab>''
+Fix target_signal_from_host() etc.
-This command should expand to a list of all supported architectures.
-At present ``info architecture'' needs to be used. That is simply
-wrong. It involves the use of add_set_enum_cmd().
+The name is wrong for starters. ``target_signal'' should probably be
+``gdb_signal''. ``from_host'' should be ``from_target_signal''.
+After that it needs to be multi-arched and made independent of any
+host signal numbering.
+
+Once this is done, the signal enum can probably be moved to
+include/gdb so that it is available to embedded stubs.
--
--
+Make MIPS pure multi-arch.
+
+It is only at the multi-arch enabled stage.
+
+--
+
Truly multi-arch.
Enable the code to recognize --enable-targets=.... like BINUTILS does.
Extra ui_file methods - dump.
-These are for debugging / testing. An aside is to set up a whitebox
-testsuite for key internals such as ui_file.
+Very useful for whitebox testing.
--
--
-Make MI interface accessable from existing CLI.
+Make MI interface accessible from existing CLI.
--
handles the correct output well. It doesn't resolve what to do with
output / error-messages when things go wrong.
+--
+
+do_setshow_command contains a 1024 byte buffer.
+
+The function assumes that there will never be any more than 1024 bytes
+of enum. It should use mem_file.
+
+--
+
+Should struct cmd_list_element . completer take the command as an
+argument?
+
+--
+
+Should the bulk of top.c:line_completion_function() be moved to
+command.[hc]? complete_on_cmdlist() and complete_on_enums() could
+then be made private.
+
+--
+
+top.c (execute_command): Should a command being valid when the target
+is running be made an attribute (predicate) to the command rather than
+an explicit set of tests.
+
+--
+
+top.c (execute_command): Should the bulk of this function be moved
+into command.[hc] so that top.c doesn't grub around in the command
+internals?
+
--
Architectural Change: Async
open an asynchronous target that may need to perform background tasks
as part of the ``attach'' phase.
-Unfortunatly, due to limitations in the old/creaking command.h
+Unfortunately, due to limitations in the old/creaking command.h
interface, that isn't possible. The function being called isn't told
of the ``xxx'' or any other context information.
for that command. Other changes such as making ``struct command''
opaque may also help.
+See also:
+http://sourceware.cygnus.com/ml/gdb-patches/2000-06/msg00062.html
+
--
Make "target xxx" command interruptible.
--
+ TODO FAQ
+ ========
+
+Frequently requested but not approved requests.
+
+--
+
+Eliminate unused argument warnings using ATTRIBUTE_UNUSED.
+
+The benefits on this one are thought to be marginal - GDBs design
+means that unused parameters are very common. GCC 3.0 will also
+include the option -Wno-unused-parameter which means that ``-Wall
+-Wno-unused-parameters -Werror'' can be specified.
+
+--
+
+
+
Legacy Wish List
================
Make single_step() insert and remove breakpoints in one operation.
+[If this is talking about having single_step() insert the breakpoints,
+run the target then pull the breakpoints then it is wrong. The
+function has to return as control has to eventually be passed back to
+the main event loop.]
+
--
Speed up single stepping by avoiding extraneous ptrace calls.
projects / deliverable / binutils-gdb.git / blobdiff