Review TODO.

gdb/ChangeLog

@@ -1,3 +1,7 @@
+Tue May 16 18:57:14 2000  Andrew Cagney  <cagney@b1.cygnus.com>
+
+	* TODO: Review.  Delete anything that is no longer applicable.
+
 Tue May 16 14:17:20 2000  Andrew Cagney  <cagney@b1.cygnus.com>
 
 	* utils.c (free_current_contents): Make more robust.

gdb/TODO

@@ -193,11 +193,11 @@ Robert Lipe writes:
 
 --
 
-			Code cleanups
+			Code Cleanups
 			=============
 
-The following code cleanups are planned for the follow-on release to
+The following are small cleanups that will hopefully be completed by
-GDB 5.0.
+the follow on to 5.0.
 
 --
 
@@ -253,14 +253,19 @@ to make a lot of changes that could potentially break each other.
 
 --
 
+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().
+
+--
+
 GDBARCH cleanup (Andrew Cagney)
 
 The non-generated parts of gdbarch.{sh,h,c} should be separated out
 into arch-utils.[hc].
 
-The ``info architecture'' command should be replaced with a fixed
-``set architecture'' (implemented using the command.c enum code).
-
 Document that gdbarch_init_ftype could easily fail because it didn't
 identify an architecture.
 
@@ -277,6 +282,18 @@ 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
 
+--
+
+			General Cleanups / Fixes
+			========================
+
+The following are more general cleanups and fixes.  They are not tied
+to any specific release.
+
+--
+
+Nuke USG define.
+
 --
 
 Eliminate gdb/tui/Makefile.in.
@@ -295,17 +312,150 @@ Do not forget to merge the patch back into the trunk.
 
 --
 
-Re: [RFC] Change configure.in so -W arnings match reality
+Update ALPHA so that it uses ``struct frame_extra_info'' instead of
-http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00350.html
+EXTRA_FRAME_INFO.
 
-Some GCC compilers do not like -Wreturn-type.  (Going forward there
+This is a barrier to replacing mips_extra_func_info with something
-may be more problems like that).  Need to check which of the warning
+that works with multi-arch.
-options are valid.  Need to probably disable warnings by default.
 
 --
 
-			General Wish List
+Multi-arch  mips_extra_func_info.
-			=================
+
+This first needs the alpha to be updated so that it uses ``struct
+frame_extra_info''.
+
+--
+
+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.
+
+--
+
+Rationalize the host-endian code (grep for HOST_BYTE_ORDER).
+
+At preent 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 asprintf() calls with xasprintf() calls.
+
+As with things like strdup() most calls to asprintf() don't check the
+return value.
+
+--
+
+Rationaize savestring(), msavestring() and mstrsave().
+
+In general libiberty's xstrdup () can be used.
+
+--
+
+Eliminate mmalloc() from GDB.
+
+Also eliminate it from defs.h.
+
+--
+
+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).
+
+--
+
+Eliminate error_begin().
+
+With ui_file, there is no need for the statefull error_begin ()
+function.
+
+--
+
+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.
+
+--
+
+Replace gdb_stdtarg with gdb_targout (and possibly gdb_targerr).
+
+gdb_stdtarg is easily confused with gdb_stdarg.
+
+--
+
+Remote protocol doco feedback.
+
+Too much feedback to mention needs to be merged in (901660).  Search
+for the word ``remote''.
+
+--
+
+set/show remote X-packet ...
+
+``(gdb) help set remote X-packet'' doesn't list the applicable
+responses.  The help message needs to be expanded.
+
+--
+
+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.
+
+--
+
+Add an "info bfd" command that displays supported object formats,
+similarly to objdump -i.
+
+Is there a command already?
+
+--
+
+			Architectural Changes
+			=====================
+
+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.
+
+--
+
+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.
+
+Unfortunatly 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.
 
 --
 
@@ -441,6 +591,155 @@ Add support for Modula3
 
 Get DEC/Compaq to contribute their Modula-3 support.
 
+--
+
+Convert ALL architectures to MULTI-ARCH.
+
+--
+
+Convert GDB build process to AUTOMAKE.
+
+--
+
+Restructure gdb directory tree so that it avoids any 8.3 and 14
+filename problems.
+
+--
+
+Can the xdep files be replaced by autoconf?
+Can the tm.h and nm.h files be eliminated by multi-arch.
+
+--
+
+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''.
+
+--
+
+Make MI interface accessable from existing CLI.
+
+--
+
+Select the initial multi-arch ISA / ABI based on --target or similar.
+
+At present the default is based on what ever is first in the BFD
+archures table.  It should be determined based on the ``--target=...''
+name.
+
+--
+
+Truly multi-arch.
+
+Enable the code to recognize --enable-targets=.... like BINUTILS does.
+
+--
+
+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.
+
+--
+
+Re-do GDB's output pager.
+
+GDB's output pager still relies on people correctly using *_filtered
+for gdb_stdout and *_unfiltered for gdb_stdlog / gdb_stderr.
+Hopefully, with all normal output going to gdb_stdout, the pager can
+just look at the ui_file that the output is on and then use that to
+decide what to do about paging.  Sounds good in theory.
+
+--
+
+Add mechanism to reject 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.
+
+--
+
+Remove sideffects from libgdb breakpoint create function.
+
+The user can use the CLI to create a breakpoint with partial
+information - no file (gdb would use the file from the last
+breakpoint).
+
+The libgdb interface currently affects that environment which can lead
+to confusion when a user is setting breakpoints via both the MI and
+the CLI.
+
+This is also a good example of how getting the CLI ``right'' will be
+hard.
+
+--
+
+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 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.
+
+--
+
+Move gdb_lasterr to ui_out?
+
+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.
+
+--
+
+Fix implementation of  ``target xxx''.
+
+At present when the user specifies ``target xxxx'', the CLI maps that
+directly onto a target open method.  It is then assumed that the
+target open method should do all sorts of complicated things as this
+is the only chance it has.  Check how the various remote targets
+duplicate the target operations.  Check also how the various targets
+behave differently for purely arbitrary reasons.
+
+What should happen is that ``target xxxx'' should call a generic
+``target'' function and that should then co-ordinate the opening of
+``xxxx''.  This becomes especially important when you're trying to
+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
+interface, that isn't possible.  The function being called isn't told
+of the ``xxx'' or any other context information.
+
+Consequently a precursor to fixing ``target xxxx'' is to clean up the
+CLI code so that it passes to the callback function (attatched to a
+command) useful information such as the actual command and a context
+for that command.  Other changes such as making ``struct command''
+opaque may also help.
+
+--
+
+Document trace machinery
+
+--
+
+Document overlay machinery.
+
 --
 
 			Legacy Wish List
@@ -452,13 +751,6 @@ always pays to check the below.
 
 --
 
-Document trace machinery.
-
-Document overlay machinery.
-
-Extend .gdbinit mechanism to specify name on command line, allow for
-lists of files to load, include function of --tclcommand.
-
 @c This does not work (yet if ever).  FIXME.
 @c @item --parse=@var{lang} @dots{}
 @c Configure the @value{GDBN} expression parser to parse the listed languages.
@@ -466,21 +758,28 @@ lists of files to load, include function of --tclcommand.
 @c list of all supported languages, omit the argument.  Without this
 @c option, @value{GDBN} is configured to parse all supported languages.
 
-Add an "info bfd" command that displays supported object formats,
+--
-similarly to objdump -i.
 
 START_INFERIOR_TRAPS_EXPECTED need never be defined to 2, since that
 is its default value.  Clean this up.
 
+--
+
 It should be possible to use symbols from shared libraries before we know
 exactly where the libraries will be loaded.  E.g. "b perror" before running
 the program.  This could maybe be done as an extension of the "breakpoint
 re-evaluation" after new symbols are loaded.
 
+--
+
 Make single_step() insert and remove breakpoints in one operation.
 
+--
+
 Speed up single stepping by avoiding extraneous ptrace calls.
 
+--
+
 Speed up single stepping by not inserting and removing breakpoints
 each time the inferior starts and stops.
 
@@ -488,160 +787,118 @@ Breakpoints should not be inserted and deleted all the time.  Only the
 one(s) there should be removed when we have to step over one.  Support
 breakpoints that don't have to be removed to step over them.
 
-Update gdbint.texinfo to include doc on the directory structure and 
+[this has resulted in numerous debates.  The issue isn't clear cut]
-the various tricks of building gdb.
 
-Do a tutorial in gdb.texinfo on how to do simple things in gdb.
+--
-E.g. how to set a breakpoint that just prints something and continues.
-How to break on aborts.  Etc.
 
 Provide "voodoo" debugging of core files.  This creates a zombie
 process as a child of the debugger, and loads it up with the data,
 stack, and regs of the core file.  This allows you to call functions
 in the executable, to manipulate the data in the core file.
 
+[you wish]
+
+--
+
 GDB reopens the source file on every line, as you "next" through it.
 
-Referencing the vtbl member of a struct doesn't work.  It prints OK
+[still true? I've a memory of this being fixed]
-if you print the struct, but it gets 0 if you try to deref it.
 
-Persistent command history: A feature where you could save off a list
+--
-of the commands you did, so you can edit it into something that will bring
-the target to the same place every time you source it.
-This would also be useful for automated fast watchpointing; if you go
-past the place where it watchpoints, you just start it over again and
-do it more carefully.
-
-Deal with the SunOS 4.0 and 4.1.1 ptrace bug that loses the registers if
-the stack is paged out.
-
-Finish the C++ exception handling stub routines.  Lint points them out
-as unused statics functions.
 
 Perhaps "i source" should take an argument like that of "list".
 
-See if core-aout.c's fetch_core_registers can be used on more machines.
+--
-E.g. MIPS (mips-xdep.c).
-
-unpack_double() does not handle IEEE float on the target unless the host
-is also IEEE.  Death on a vax.
-
-Set up interface between GDB and INFO so that you can hop into interactive
-INFO and back out again.  When running under Emacs, should use Emacs
-info, else fork the info program.  Installation of GDB should install
-its texinfo files into the info tree automagically, including the readline
-texinfo files.
-
-"help address" ought to find the "help set print address" entry.
-
-Remove the VTBL internal guts from printouts of C++ structs, unless
-vtblprint is set.
 
 Remove "at 0xnnnn" from the "b foo" response, if `print address off' and if
 it matches the source line indicated.
 
+--
+
 The prompt at end of screen should accept space as well as CR.
 
-Check STORE_RETURN_VALUE on all architectures.  Check near it in tm-sparc.h
+--
-for other bogosities.
-
-Check for storage leaks in GDB, I'm sure there are a lot!
-
-vtblprint of a vtbl should demangle the names it's printing.
 
 Backtrace should point out what the currently selected frame is, in
 its display, perhaps showing "@3 foo (bar, ...)" or ">3 foo (bar,
 ...)" rather than "#3 foo (bar, ...)".
 
+--
+
 "i program" should work for core files, and display more info, like what
 actually caused it to die.
 
+--
+
 "x/10i" should shorten the long name, if any, on subsequent lines.
 
-Check through the code for FIXME comments and fix them.  dbxread.c,
+--
-blockframe.c, and plenty more. (I count 634 as of 940621 - sts)
 
 "next" over a function that longjumps, never stops until next time you happen
 to get to that spot by accident.  E.g. "n" over execute_command which has
 an error.
 
+--
+
 "set zeroprint off", don't bother printing members of structs which
 are entirely zero.  Useful for those big structs with few useful
 members.
 
+--
+
 GDB does four ioctl's for every command, probably switching terminal modes
 to/from inferior or for readline or something.
 
+--
+
 terminal_ours versus terminal_inferior: cache state.  Switch should be a noop
 if the state is the same, too.
 
-ptype $i6 = void??!
+--
-
-Clean up invalid_float handling so gdb doesn't coredump when it tries to
-access a NaN.  While this might work on SPARC, other machines are not
-configured right.
-
-"b value_at ; commands ; continue ; end" stops EVERY OTHER TIME!
-Then once you enter a command, it does the command, runs two more
-times, and then stops again!  Bizarre...  (This behaviour has been
-modified, but it is not yet 100% predictable when e.g. the commands
-call functions in the child, and while there, the child is interrupted
-with a signal, or hits a breakpoint.)
-
-help completion, help history should work.
-
-Check that we can handle stack trace through varargs AND alloca in same
-function, on 29K.
-
-wait_for_inferior loops forever if wait() gives it an error.
 
 "i frame" shows wrong "arglist at" location, doesn't show where the args
 should be found, only their actual values.
 
+--
+
 There should be a way for "set" commands to validate the new setting
 before it takes effect.
 
-A mess of floating point opcodes are missing from sparc-opcode.h.
+--
-Also, a little program should test the table for bits that are
-overspecified or underspecified.  E.g. if the must-be-ones bits
-and the must-be-zeroes bits leave some fields unexamined, and the format
-string leaves them unprinted, then point this out.  If multiple
-non-alias patterns match, point this out too.  Finally, there should
-be a sparc-optest.s file that tries each pattern out.  This file
-should end up coming back the same (modulo transformation comments) 
-if fed to "gas" then the .o is fed to gdb for disassembly.
-
-Eliminate all the core_file_command's in all the xdep files.
-Eliminate separate declarations of registers[] everywhere.
 
 "ena d" is ambiguous, why?  "ena delete" seems to think it is a command!
 
-Perhaps move the tdep, xdep, and nat files, into the config
+--
-subdirectories.  If not, at least straighten out their names so that
-they all start with the machine name.
-
-inferior_status should include stop_print_frame.  It won't need to be
-reset in wait_for_inferior after bpstat_stop_status call, then.
 
 i line VAR produces "Line number not known for symbol ``var''.".  I
 thought we were stashing that info now!
 
+--
+
 We should be able to write to random files at hex offsets like adb.
 
+--
+
 Make "target xxx" command interruptible.
 
+--
+
+[elena - delete this]
+
 Handle add_file with separate text, data, and bss addresses.  Maybe
 handle separate addresses for each segment in the object file?
 
+--
+
+[Jimb/Elena delete this one]
+
 Handle free_named_symtab to cope with multiply-loaded object files
 in a dynamic linking environment.  Should remember the last copy loaded,
 but not get too snowed if it finds references to the older copy.
 
-Generalize and Standardize the RPC interface to a target program,
+--
-improve it beyond the "ptrace" interface, and see if it can become a
+
-standard for remote debugging.  (This is talking about the vxworks
+[elena delete this also]
-interface.  Seems unlikely to me that there will be "a standard" for
-remote debugging anytime soon --kingdon, 8 Nov 1994).
 
 Remove all references to:
 	text_offset
@@ -652,42 +909,26 @@ Remove all references to:
 	...
 now that we have BFD.  All remaining are in machine dependent files.
 
-When quitting with a running program, if a core file was previously
+--
-examined, you get "Couldn't read float regs from core file"...if 
-indeed it can't.  generic_mourn_inferior...
-
-Have remote targets give a warning on a signal argument to
-target_resume.  Or better yet, extend the protocols so that it works
-like it does on the Unix-like systems.
-
-Sort help and info output.
 
 Re-organize help categories into things that tend to fit on a screen
 and hang together.
 
-renote-nindy.c handles interrupts poorly; it error()s out of badly
+--
-chosen places, e.g. leaving current_frame zero, which causes core dumps
-on the next command.
 
 Add in commands like ADB's for searching for patterns, etc.  We should
 be able to examine and patch raw unsymboled binaries as well in gdb as
 we can in adb.  (E.g. increase the timeout in /bin/login without source).
 
-Those xdep files that call register_addr without defining it are
+[actually, add ADB interface :-]
-probably simply broken.  When reconfiguring this part of gdb, I could
+
-only make guesses about how to redo some of those files, and I
+--
-probably guessed wrong, or left them "for later" when I have a
-machine that can attempt to build them.
 
 When doing "step" or "next", if a few lines of source are skipped between
 the previous line and the current one, print those lines, not just the
 last line of a multiline statement.
 
-When searching for C++ superclasses in value_cast in valops.c, we must
+--
-not search the "fields", only the "superclasses".  There might be a
-struct with a field name that matches the superclass name.  This can
-happen when the struct was defined before the superclass (before the
-name became a typedef).
 
 Handling of "&" address-of operator needs some serious overhaul
 for ANSI C and consistency on arrays and functions.
@@ -699,65 +940,75 @@ ptype &malloc     ==> "char *(*)()"
 call printf ("%x\n", malloc)   ==> weird value, should be same as
 call printf ("%x\n", &malloc)  ==> correct value
 
+--
+
 Fix dbxread.c symbol reading in the presence of interrupts.  It
 currently leaves a cleanup to blow away the entire symbol table when a
 QUIT occurs.  (What's wrong with that? -kingdon, 28 Oct 1993).
 
+[I suspect that the grype was that, on a slow system, you might want
+to cntrl-c and get just half the symbols and then load the rest later
+- scary to be honest]
+
+--
+
 Mipsread.c reads include files depth-first, because the dependencies
 in the psymtabs are way too inclusive (it seems to me).  Figure out what
 really depends on what, to avoid recursing 20 or 30 times while reading
 real symtabs.
 
+--
+
 value_add() should be subtracting the lower bound of arrays, if known,
 and possibly checking against the upper bound for error reporting.
 
-mipsread.c symbol table allocation and deallocation should be checked.
+--
-My suspicion is that it's full of memory leaks.
-
-SunOS should have a target_lookup_symbol() for common'd things allocated
-by the shared library linker ld.so.
 
 When listing source lines, check for a preceding \n, to verify that
 the file hasn't changed out from under us.
 
-When listing source lines, eat leading whitespace corresponding to the
+[fixed by some other means I think.  That hack wouldn't actually work
-line-number prefix we print.  This avoids long lines wrapping.
+reliably - the file might move such that another \n appears. ]
 
-mipsread.c needs to check for old symtabs and psymtabs for the same
+--
-files, the way it happens for dbxread.c and coffread.c, for VxWorks
-incremental symbol table reloading.
 
 Get all the remote systems (where the protocol allows it) to be able to
 stop the remote system when the GDB user types ^C (like remote.c
 does).  For ebmon, use ^Ak.
 
+--
+
 Possible feature: A version of the "disassemble" command which shows
 both source and assembly code ("set symbol-filename on" is a partial
 solution).
 
+[has this been done?  It was certainly done for MI and GDBtk]
+
+--
+
 investigate "x/s 0" (right now stops early) (I think maybe GDB is
 using a 0 address for bad purposes internally).
 
+--
+
 Make "info path" and path_command work again (but independent of the
 environment either of gdb or that we'll pass to the inferior).
 
+--
+
 Make GDB understand the GCC feature for putting octal constants in
 enums.  Make it so overflow on an enum constant does not error_type
 the whole type.  Allow arbitrarily large enums with type attributes.
 Put all this stuff in the testsuite.
 
+--
+
 Make TYPE_CODE_ERROR with a non-zero TYPE_LENGTH more useful (print
 the value in hex; process type attributes).  Add this to the
 testsuite.  This way future compilers can add new types and old
 versions of GDB can do something halfway reasonable.
 
-Clean up formatting of "info registers" on MIPS and 88k.  See if it
+--
-is possible to do this generically across all target architectures.
-
-GDB gets bfd/corefile.c and gdb/corefile.c confused (this should be easy to
-repeat even with something more recent than GDB 4.9).
-
-Check that unmatched RBRAC doesn't abort().
 
 Fix mdebugread.c:parse_type to do fundamental types right (see
 rs6000_builtin_type in stabsread.c for what "right" is--the point is
@@ -766,49 +1017,42 @@ depend on stuff like TARGET_PTR_BIT and so on.  For mdebug, there seem
 to be separate bt* codes for 64 bit and 32 bit things, and GDB should
 be aware of that).  Also use a switch statement for clarity and speed.
 
+--
+
 Investigate adding symbols in target_load--some targets do, some
 don't.
 
+--
+
 Put dirname in psymtabs and change lookup*symtab to use dirname (so
 /foo/bar.c works whether compiled by cc /foo/bar.c, or cd /foo; cc
 bar.c).
 
+--
+
 Merge xcoffread.c and coffread.c.  Use breakpoint_re_set instead of
 fixup_breakpoints.
 
-Fix byte order and int size sins in tm-a29k.h
+--
-(EXTRACT_RETURN_VALUE).  Perhaps should reproduce bug and verify fix
-(or perhaps should just fix it...).
-
-Make a watchpoint on a constant expression an error (or warning
-perhaps)
 
 Make a watchpoint which contains a function call an error (it is
 broken now, making it work is probably not worth the effort).
 
-Re-do calls to signal() in remote.c, and inflow.c (set_sigint_trap and
+--
-so on) to be independent of the debugging target, using target_stop to
-stop the inferior.  Probably the part which is now handled by
-interrupt_query in remote.c can be done without any new features in
-the debugging target.
 
 New test case based on weird.exp but in which type numbers are not
 renumbered (thus multiply defining a type).  This currently causes an
 infinite loop on "p v_comb".
 
-Nuke baseclass_addr.
+--
 
-Nuke USG define.
+[Hey! Hint Hint Delete Delete!!!]
-
-"source file more recent" loses on re-read
 
 Fix 386 floating point so that floating point registers are real
 registers (but code can deal at run-time if they are missing, like
 mips and 68k).  This would clean up "info float" and related stuff.
 
-Look at Solaris bug in interrupt.exp.  Can get out of syscall with
+--
-PRSABORT (syscall will return EINTR) but merely doing that leads to a
-"can't read memory" error.
 
 gcc -g -c enummask.c then gdb enummask.o, then "p v".  GDB complains
 about not being able to access memory location 0.
@@ -832,49 +1076,33 @@ enum mask
   LARGE = 0x20
 } v;
 
+--
+
 If try to modify value in file with "set write off" should give
 appropriate error not "cannot access memory at address 0x65e0".
 
-Why do we allow a target to omit standard register names (NO_STD_REGS
+--
-in tm-z8k.h)?  I thought the standard register names were supposed to
-be just that, standard.
 
 Allow core file without exec file on RS/6000.
 
+--
+
 Make sure "shell" with no arguments works right on DOS.
 
+--
+
 Make gdb.ini (as well as .gdbinit) be checked on all platforms, so
 the same directory can be NFS-mounted on unix or DOS, and work the
 same way.
 
-cd ~/tmp/<M-?> causes infinite loop (where ~/tmp is a directory).
+--
+
+[Is this another delete???]
 
 Get SECT_OFF_TEXT stuff out of objfile_relocate (might be needed to
 get RS/6000 to work right, might not be immediately relevant).
 
-Clean up add_toc_to_loadinfo
+--
-
-Think about attached processes and sharing terminal.
-
-John sez in reference to ignoring errors from tcsegpgrp if attach_flag:
-set_tty_state should not have any trouble with attached processes.
-Instead, the tty handling should leave the pgrp of the tty alone when
-attaching to processes (perhaps pass terminal_init_inferior a flag
-saying whether we're attaching).
-
-PAGE_SIZE redefined warnings on AIX.  Probably should be using
-BFD_PAGE_SIZE throughout BFD.
-
-Rewrite proceed, wait_for_inferior, and normal_stop to clean them up.
-Suggestions: 
-
-	1) Make each test in wait_for_inferior a seperate subroutine
-	   call.
-	2) Combine wait_for_inferior and normal_stop to clean up
-	   communication via global variables.
-	3) See if you can find some way to clean up the global
-	   variables that are used; possibly group them by data flow
-	   and information content?
 
 Work out some kind of way to allow running the inferior to be done as
 a sub-execution of, eg. breakpoint command lists.  Currently running
@@ -882,26 +1110,26 @@ the inferior interupts any command list execution.  This would require
 some rewriting of wait_for_inferior & friends, and hence should
 probably be done in concert with the above.
 
+--
+
 Add function arguments to gdb user defined functions.
 
+--
+
 Add convenience variables that refer to exec file, symbol file,
 selected frame source file, selected frame function, selected frame
 line number, etc.
 
+--
+
 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.
 
-Add stab information to allow reasonable debugging of inline functions
+[hey async!!]
-(possibly they should show up on a stack backtrace?  With a note
-indicating that they weren't "real"?).
 
-Modify the naked "until" command to step until past the current source
+--
-line, rather than past the current pc value.  This is tricky simply
-because the low level routines have no way of specifying a multi-line
-step range, and there is no way of saying "don't print stuff when we
-stop" from above (otherwise could just call step many times).
 
 Modify the handling of symbols grouped through BINCL/EINCL stabs to
 allocate a partial symtab for each BINCL/EINCL grouping.  This will
@@ -909,17 +1137,20 @@ seriously decrease the size of inter-psymtab dependencies and hence
 lessen the amount that needs to be read in when a new source file is
 accessed. 
 
-Do an "x/i $pc" after each stepi or nexti.  
+--
 
-Modify all of the disassemblers to use printf_filtered to get correct
+[Comming...]
-more filtering.
 
 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).
 
+--
+
 Remove the range and type checking code and documentation, if not
 going to implement.