-Asynchronous expression evaluator
-
-Inferior function calls hang GDB.
-
---
-
-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.
-
---
-
-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.
-
---
-
-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
- ================
-
-This list is not up to date, and opinions vary about the importance or
-even desirability of some of the items. If you do fix something, it
-always pays to check the below.
-
---
-
-@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.
-@c @samp{all} configures @value{GDBN} for all supported languages. To get a
-@c list of all supported languages, omit the argument. Without this
-@c option, @value{GDBN} is configured to parse all supported languages.
-
---
-
-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.
-
-[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.
-
---
-
-Speed up single stepping by not inserting and removing breakpoints
-each time the inferior starts and stops.
-
-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.
-
-[this has resulted in numerous debates. The issue isn't clear cut]
-
---
-
-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.
-
-[still true? I've a memory of this being fixed]
-
---
-
-Perhaps "i source" should take an argument like that of "list".
-
---
-
-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.
-
---
-
-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.
-
---
-
-"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.
-
---
-
-"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.
-
---
-
-"ena d" is ambiguous, why? "ena delete" seems to think it is a command!
-
---
-
-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.
-
---
-
-[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.
-
---
-
-[elena delete this also]
-
-Remove all references to:
- text_offset
- data_offset
- text_data_start
- text_end
- exec_data_offset
- ...
-now that we have BFD. All remaining are in machine dependent files.
-
---
-
-Re-organize help categories into things that tend to fit on a screen
-and hang together.
-
---
-
-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).
-
-[actually, add ADB interface :-]
-
---
-
-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.
-
---
-
-Handling of "&" address-of operator needs some serious overhaul
-for ANSI C and consistency on arrays and functions.
- For "float point[15];":
-ptype &point[4] ==> Attempt to take address of non-lvalue.
- For "char *malloc();":
-ptype malloc ==> "char *()"; should be same as
-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.
-
---
-
-When listing source lines, check for a preceding \n, to verify that
-the file hasn't changed out from under us.
-
-[fixed by some other means I think. That hack wouldn't actually work
-reliably - the file might move such that another \n appears. ]
-
---
-
-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.
-
---
-
-Fix mdebugread.c:parse_type to do fundamental types right (see
-rs6000_builtin_type in stabsread.c for what "right" is--the point is
-that the debug format fixes the sizes of these things and it shouldn't
-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.
-
---
-
-Make a watchpoint which contains a function call an error (it is
-broken now, making it work is probably not worth the effort).
-
---
-
-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".
-
---
-
-[Hey! Hint Hint Delete Delete!!!]
-
-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.
-
---
-
-gcc -g -c enummask.c then gdb enummask.o, then "p v". GDB complains
-about not being able to access memory location 0.
-
--------------------- enummask.c
-enum mask
-{
- ANIMAL = 0,
- VEGETABLE = 1,
- MINERAL = 2,
- BASIC_CATEGORY = 3,
-
- WHITE = 0,
- BLUE = 4,
- GREEN = 8,
- BLACK = 0xc,
- COLOR = 0xc,
-
- ALIVE = 0x10,
-
- 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".
-
---
-
-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.
-
---
-
-[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).
-
---
-
-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
-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.
-
---
-
-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
-lessen the amount that needs to be read in when a new source file is
-accessed.
-
---
-
-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.
-