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.
+
+ o typedef and structs
+
+ o ISO-C
+
+and most likely also:
+
+ o include conventions
--
-GDB requires GCC to build under IRIX
+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:
-IRIX, being more pedantic than GCC reports as errors certain
-assignments that GCC treats as warnings.
+ http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00230.html
-This can be worked around by building GDB with the GCC compiler.
+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
--
-The BFD directory requires bug-fixed AUTOMAKE et.al.
+x86 linux GDB and SIGALRM (???)
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00803.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
+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]
--
-Generic: lin-thread cannot handle thread exit (Mark Kettenis, Michael
-Snyder) http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00525.html
+RFD: infrun.c: No bpstat_stop_status call after proceed over break?
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00665.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.
+GDB misses watchpoint triggers after proceeding over a breakpoint on
+x86 targets.
-As an additional reference point, the pre thread_db code did not work
-either.
+--
+
+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 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: 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.
+
--
-Pascal (Pierre Muller, David Taylor)
+ GDB 5.1 - Cleanups
+ ==================
-Pierre Muller has contributed patches for adding Pascal Language
-support to GDB.
+The following code cleanups will hopefully be applied to GDB 5.1.
-2 pascal language patches inserted in database
-http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00521.html
+-- 2001-03-22
-Indent -gnu ?
-http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00496.html
+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
--
-GNU/Linux/x86 and random thread signals (and Solaris/SPARC but not
-Solaris/x86).
-http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00336.html
+Change documentation to GFDL license.
-Christopher Blizzard writes:
+``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?
-So, I've done some more digging into this and it looks like Jim
-Kingdon has reported this problem in the past:
+The GFDL and some instructions for using it can be found in
+http://www.gnu.org/copyleft/''
-http://sourceware.cygnus.com/ml/bug-gdb/1999-10/msg00058.html
+ RMS
-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:
+Fix copyright notices.
-when debugging threaded applications you get extra SIGTRAPs
-http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=9565
+Turns out that ``1998-2000'' isn't considered valid :-(
-[There should be a GDB testcase - cagney]
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00467.html
--
-Possible regressions with some devel GCCs.
-http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00475.html
+ GDB 5.1 - Known Problems
+ ========================
-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
+--
+
+z8k
-This should now be fixed.
+The z8k has suffered bit rot and is known to not build. The problem
+was occuring in the opcodes directory.
--
-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
+Solaris 8 x86 CURSES_H problem
+http://sources.redhat.com/ml/gdb/2000-07/msg00038.html
-GDB misses watchpoint triggers after proceeding over a breakpoint on
-x86 targets.
+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.
--
-x86 linux GDB and SIGALRM (???)
-http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00803.html
+ GDB 5.2 - Fixes
+ ===============
+
+--
-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.
+Thread support. Right now, as soon as a thread finishes and exits,
+you're hosed. This problem is reported once a week or so.
-Mark
+--
+
+ GDB 5.2 - New features
+ ======================
--
-Revised UDP support (was: Re: [Fwd: [patch] UDP transport support])
-http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00000.html
+GCC 3.0 ABI support (but hopefully sooner...).
-(Broken) support for GDB's remote protocol across UDP is to be
-included in the follow-on release.
+--
+
+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}().
--
> 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...
--
-GDB5 TOT on unixware 7
-http://sourceware.cygnus.com/ml/gdb/2000-04/msg00119.html
+Follow through `make check' with --enable-shared.
-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.
+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?
--
- Code Cleanups
- =============
+The BFD directory requires bug-fixed AUTOMAKE et.al.
-The following are small cleanups that will hopefully be completed by
-the follow on to 5.0.
+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
--
-ATTRIBUTE_UNUSED
+Find something better than DEFAULT_BFD_ARCH, DEFAULT_BFD_VEC to
+determine the default isa/byte-order.
+
+--
-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.
--
--
-Delete macro TARGET_BYTE_ORDER_SELECTABLE.
+Elimination of ``(catch_errors_ftype *) func''.
-Patches in the database.
+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
--
-Updated readline
+Nuke #define CONST_PTR.
+
+--
-Readline 4.? is out. A merge wouldn't hurt.
+Nuke USG define.
--
-Purge PARAMS
+[PATCH/5] src/intl/Makefile.in:distclean additions
+http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00363.html
-Eliminate all uses of PARAMS in GDB's source code.
+Do not forget to merge the patch back into the trunk.
--
-Elimination of make_cleanup_func. (Andrew Cagney)
+Rationalize the host-endian code (grep for HOST_BYTE_ORDER).
-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
+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.
--
-Elimination of ``(catch_errors_ftype *) func''.
+Replace savestring() with something from libiberty.
-Like make_cleanup_func it isn't portable.
+An xstrldup()? but that would have different semantics.
--
-Re: Various C++ things
+Rationalize use of floatformat_unknown in GDB sources.
-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.
+Instead of defaulting to floatformat_unknown, should hosts/targets
+specify the value explicitly?
-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.
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00447.html
-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 a ``name'' member to include/floatformat.h:struct floatformat.
+Print that name in gdbarch.c.
--
-Fix ``set architecture <tab>''
-
-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().
+Sort out the harris mess in include/floatformat.h (it hardwires two
+different floating point formats).
--
-GDBARCH cleanup (Andrew Cagney)
+See of the GDB local floatformat_do_doublest() and libiberty's
+floatformat_to_double (which was once GDB's ...) can be merged some
+how.
-The non-generated parts of gdbarch.{sh,h,c} should be separated out
-into arch-utils.[hc].
+--
-Document that gdbarch_init_ftype could easily fail because it didn't
-identify an architecture.
+Eliminate mmalloc(), mstrsave() et.al. from GDB.
+
+Also eliminate it from defs.h.
--
-Migrate qfThreadInfo packet -> qThreadInfo. (Andrew Cagney)
+Eliminate PTR. ISO-C allows ``void *''.
-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
+Eliminate abort ().
-[PATCH] "info threads" queries for remote.c
-http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00831.html
+GDB should never abort. GDB should either throw ``error ()'' or
+``internal_error ()''. Better still GDB should naturally unwind with
+an error status.
--
- General Cleanups / Fixes
- ========================
+GDB probably doesn't build on FreeBSD pre 2.2.x
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00378.html
-The following are more general cleanups and fixes. They are not tied
-to any specific release.
+Fixes to get FreeBSD working on 2.2.x, 3.x and 4.x caused the code to
+suffer bit rot.
--
-Nuke USG define.
+Deprecate "fg". Apparently ``fg'' is actually continue.
+
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00417.html
--
-[PATCH/5] src/intl/Makefile.in:distclean additions
-http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00363.html
+Deprecate current use of ``floatformat_unknown''.
-Do not forget to merge the patch back into the trunk.
+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
--
-Update ALPHA so that it uses ``struct frame_extra_info'' instead of
-EXTRA_FRAME_INFO.
+Rationalize floatformat_to_double() vs floatformat_to_doublest().
-This is a barrier to replacing mips_extra_func_info with something
-that works with multi-arch.
+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
--
-Multi-arch mips_extra_func_info.
+Move floatformat_ia64_ext to libiberty/include floatformat.[ch].
-This first needs the alpha to be updated so that it uses ``struct
-frame_extra_info''.
+http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00466.html
--
-Send normal output to gdb_stdout.
-Send error messages to gdb_stderror.
-Send debug and log output log gdb_stdlog.
+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?
-GDB still contains many cases where (f)printf or printf_filtered () is
-used when it should be sending the messages to gdb_stderror or
-gdb_stdlog. The thought of #defining printf to something has crossed
-peoples minds ;-)
+--
+
+When tab expanding something like ``set arch<tab>'' ignore the
+deprecated ``set archdebug'' and expand to ``set architecture''.
--
-Rationalize the host-endian code (grep for HOST_BYTE_ORDER).
+Eliminate ``arm_register_names[j] = (char *) regnames[j]'' and the
+like from arm-tdep.c.
-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.
+--
+
+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.
--
-Replace asprintf() calls with xasprintf() calls.
+IRIX 3.x support is probably broken.
-As with things like strdup() most calls to asprintf() don't check the
-return value.
+--
+
+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).
--
-Rationaize savestring(), msavestring() and mstrsave().
+Move remote_remove_hw_breakpoint, remote_insert_hw_breakpoint,
+remote_remove_watchpoint, remote_insert_watchpoint into target vector.
+
+--
-In general libiberty's xstrdup () can be used.
+Eliminate ``extern'' from C files.
--
-Eliminate mmalloc() from GDB.
+Replace ``STREQ()'' et.al. with ``strcmp() == 0'' et.al.
-Also eliminate it from defs.h.
+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.
--
-Check/cleanup MI documentation.
+Resolve how to handle a target that changes things like its endianess
+on the fly - should it be returned in the ``T'' packet?
-The list of commands specified in the documentation needs to be
-checked against the mi-cmds.c table in a mechanical way (so that they
-two can be kept up-to-date).
+Underlying problem is that the register file is target endian. If the
+target endianess changes gdb doesn't know.
--
-Eliminate error_begin().
+ Symbol Support
+ ==============
-With ui_file, there is no need for the statefull error_begin ()
-function.
+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).
-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.
+Investiagate ways of reducing memory.
--
-Replace gdb_stdtarg with gdb_targout (and possibly gdb_targerr).
-
-gdb_stdtarg is easily confused with gdb_stdarg.
+Investigate ways of improving load time.
--
-Remote protocol doco feedback.
+Get the d10v to use POINTER_TO_ADDRESS and ADDRESS_TO_POINTER.
-Too much feedback to mention needs to be merged in (901660). Search
-for the word ``remote''.
+Consequence of recent symtab clarification. No marks for figuring out
+who maintains the d10v.
--
-set/show remote X-packet ...
+Get the MIPS to correctly sign extend all address <-> pointer
+conversions.
-``(gdb) help set remote X-packet'' doesn't list the applicable
-responses. The help message needs to be expanded.
+Consequence of recent symtab clarification. No marks for figuring out
+who maintains the MIPS.
--
-Extra ui_file methods - dump.
+GDB truncates 64 bit enums.
-These are for debugging / testing. An aside is to set up a whitebox
-testsuite for key internals such as ui_file.
+http://sourceware.cygnus.com/ml/gdb-patches/2000-06/msg00290.html
--
-Add an "info bfd" command that displays supported object formats,
-similarly to objdump -i.
+ Testsuite Support
+ =================
-Is there a command already?
+There are never to many testcases.
--
-Eliminate PTR. ISO-C allows ``void *''.
+Better thread testsuite.
--
-Eliminate abort ().
+Better C++ testsuite.
-GDB should never abort. GDB should either throw ``error ()'' or
-``internal_error ()''. Better still GDB should naturally unwind with
-an error status.
+--
+
+Look at adding a GDB specific testsuite directory so that white box
+tests of key internals can be added (eg ui_file).
--
-GDB probably doesn't build on FreeBSD pre 2.2.x
-http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00378.html
+Separate out tests that involve the floating point (FP).
-Fixes to get FreeBSD working on 2.2.x, 3.x and 4.x caused the code to
-suffer bit rot.
+(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
- =====================
+ Architectural Changes: General
+ ==============================
These are harder than simple cleanups / fixes and, consequently
involve more work. Typically an Architectural Change will be broken
--
+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
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.
--
-MI's input does not use buffering.
-
-At present the MI interface reads raw characters of from an unbuffered
-FD. This is to avoid several nasty buffer/race conditions. That code
-should be changed so that it registers its self with the event loop
-(on the input FD) and then push commands up to MI as they arrive.
-
-The serial code already does this.
-
---
-
Register Cache Cleanup (below from Andrew Cagney)
I would depict the current register architecture as something like:
|
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 ``I'm sorry, Dave, I can't do that.'' from symfile.c.
-
-This requires internationalization.
-
---
-
Check that GDB can handle all BFD architectures (Andrew Cagney)
There should be a test that checks that BFD/GDB are in sync with
--
-Add support for Modula3
+ Architectural Change: Multi-arch et al.
+ =======================================
-Get DEC/Compaq to contribute their Modula-3 support.
+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.
-Convert ALL architectures to MULTI-ARCH.
+It should be noted that ``gdbarch'' is really ``gdbabi'' and
+``gdbisa''. Once things are multi-arched breaking that down correctly
+will become much easier.
--
-Convert GDB build process to AUTOMAKE.
+GDBARCH cleanup (Andrew Cagney)
-See also sub-directory configure below.
+The non-generated parts of gdbarch.{sh,h,c} should be separated out
+into arch-utils.[hc].
+
+Document that gdbarch_init_ftype could easily fail because it didn't
+identify an architecture.
--
-Cleanup configury support for optional sub-directories.
+Fix BELIEVE_PPC_PROMOTION. Change it to BELIEVE_PPC_PROMOTION_P?
-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.
+At present there is still #ifdef BELIEVE_PPC_PROMOTION code in the
+symtab file.
-See also automake above.
+--
+
+Fix target_signal_from_host() etc.
+
+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.
--
-Restructure gdb directory tree so that it avoids any 8.3 and 14
-filename problems.
+Update ALPHA so that it uses ``struct frame_extra_info'' instead of
+EXTRA_FRAME_INFO.
+
+This is a barrier to replacing mips_extra_func_info with something
+that works with multi-arch.
--
-Can the xdep files be replaced by autoconf?
-Can the tm.h and nm.h files be eliminated by multi-arch.
+Multi-arch mips_extra_func_info.
+
+This first needs the alpha to be updated so that it uses ``struct
+frame_extra_info''.
--
-Add a transcript mechanism to GDB.
+Rationalize TARGET_SINGLE_FORMAT and TARGET_SINGLE_BIT et al.
-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''.
+Surely one of them is redundant.
--
-Make MI interface accessable from existing CLI.
+Convert ALL architectures to MULTI-ARCH.
--
--
+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.
+Can the tm.h and nm.h files be eliminated by multi-arch.
+
--
-Add a breakpoint-edit command to MI.
+ Architectural Change: MI, LIBGDB and scripting languages
+ ========================================================
-It would be similar to MI's breakpoint create but would apply to an
-existing breakpoint. It saves the need to delete/create breakpoints
-when ever they are changed.
+See also architectural changes related to the event loop. LIBGDB
+can't be finished until there is a generic event loop being used by
+all targets.
+
+The long term objective is it to be possible to integrate GDB into
+scripting languages.
--
-Add directory path to MI breakpoint.
+Implement generic ``(gdb) commmand > file''
-That way the GUI's task of finding the file within which the
-breakpoint was set is simplified.
+Once everything is going through ui_file it should be come fairly
+easy.
+
+http://sourceware.cygnus.com/ml/gdb/2000-04/msg00104.html
+
+--
+
+Replace gdb_stdtarg with gdb_targout (and possibly gdb_targerr).
+
+gdb_stdtarg is easily confused with gdb_stdarg.
+
+--
+
+Extra ui_file methods - dump.
+
+Very useful for whitebox testing.
+
+--
+
+Eliminate error_begin().
+
+With ui_file, there is no need for the statefull error_begin ()
+function.
+
+--
+
+Send normal output to gdb_stdout.
+Send error messages to gdb_stderror.
+Send debug and log output log gdb_stdlog.
+
+GDB still contains many cases where (f)printf or printf_filtered () is
+used when it should be sending the messages to gdb_stderror or
+gdb_stdlog. The thought of #defining printf to something has crossed
+peoples minds ;-)
--
--
-Add mechanism to reject expression classes to MI
+Check/cleanup MI documentation.
+
+The list of commands specified in the documentation needs to be
+checked against the mi-cmds.c table in a mechanical way (so that they
+two can be kept up-to-date).
+
+--
+
+Convert MI into libgdb
+
+MI provides a text interface into what should be many of the libgdb
+functions. The implementation of those functions should be separated
+into the MI interface and the functions proper. Those functions being
+moved to gdb/lib say.
+
+--
+
+Create libgdb.h
+
+The first part can already be found in defs.h.
+
+--
+
+MI's input does not use buffering.
+
+At present the MI interface reads raw characters of from an unbuffered
+FD. This is to avoid several nasty buffer/race conditions. That code
+should be changed so that it registers its self with the event loop
+(on the input FD) and then push commands up to MI as they arrive.
+
+The serial code already does this.
+
+--
+
+Make MI interface accessible from existing CLI.
+
+--
+
+Add a breakpoint-edit command to MI.
+
+It would be similar to MI's breakpoint create but would apply to an
+existing breakpoint. It saves the need to delete/create breakpoints
+when ever they are changed.
+
+--
+
+Add directory path to MI breakpoint.
+
+That way the GUI's task of finding the file within which the
+breakpoint was set is simplified.
+
+--
+
+Add a mechanism to reject certain expression classes to MI
There are situtations where you don't want GDB's expression
parser/evaluator to perform inferior function calls or variable
-assignments.
+assignments. A way of restricting the expression parser so that such
+operations are not accepted would be very helpful.
--
--
-GDB doesn't recover gracefully from remote protocol errors.
+Move gdb_lasterr to ui_out?
-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.
+The way GDB throws errors and records them needs a re-think. ui_out
+handles the correct output well. It doesn't resolve what to do with
+output / error-messages when things go wrong.
-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
-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.
+--
+
+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.
--
-Move gdb_lasterr to ui_out?
+Should struct cmd_list_element . completer take the command as an
+argument?
-The way GDB throws errors and records them needs a re-think. ui_out
-handles the correct output well. It doesn't resolve what to do with
-output / error-messages when things go wrong.
+--
+
+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
+ ===========================
+
+While GDB uses an event loop when prompting the user for input. That
+event loop is not exploited by targets when they allow the target
+program to continue. Typically targets still block in (target_wait())
+until the program again halts.
+
+The closest a target comes to supporting full asynchronous mode are
+the remote targets ``async'' and ``extended-async''.
+
+--
+
+Asynchronous expression evaluator
+
+Inferior function calls hang GDB.
--
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
+
--
-Document trace machinery
+Make "target xxx" command interruptible.
+
+As things become async this becomes possible. A target would start
+the connect and then return control to the event loop. A cntrl-c
+would notify the target that the operation is to be abandoned and the
+target code could respond.
--
-Document overlay machinery.
+Add a "suspend" subcommand of the "continue" command to suspend gdb
+while continuing execution of the subprocess. Useful when you are
+debugging servers and you want to dodge out and initiate a connection
+to a server running under gdb.
+
+[hey async!!]
+
+--
+
+ 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.
--
-Make "target xxx" command interruptible.
-
---
-
[elena - delete this]
Handle add_file with separate text, data, and bss addresses. Maybe
--
-Add a "suspend" subcommand of the "continue" command to suspend gdb
-while continuing execution of the subprocess. Useful when you are
-debugging servers and you want to dodge out and initiate a connection
-to a server running under gdb.
-
-[hey async!!]
-
---
-
Modify the handling of symbols grouped through BINCL/EINCL stabs to
allocate a partial symtab for each BINCL/EINCL grouping. This will
seriously decrease the size of inter-psymtab dependencies and hence
--
-[Comming...]
-
-Modify gdb to work correctly with Pascal.
-
---
-
Add a command for searching memory, a la adb. It specifies size,
mask, value, start address. ADB searches until it finds it or hits
an error (or is interrupted).
projects / deliverable / binutils-gdb.git / blobdiff