Perhaps "i source" should take an argument like that of "list".
-See if coredep.c's fetch_core_registers can be used on more machines.
+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
to get to that spot by accident. E.g. "n" over execute_command which has
an error.
-Watchpoints seem not entirely reliable, though they haven't failed me recently.
-
-"set zeroprint off", don't bother printing members of structs which are entirely
-zero. Useful for those big structs with few useful members.
+"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.
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.
+standard for remote debugging. (This is talking about the vxworks
+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
both source and assembly code ("set symbol-filename on" is a partial
solution).
-xcoffexec.c should be eliminated, contents going into either exec.c
-or rs6000-nat.c.
-
investigate "x/s 0" (right now stops early) (I think maybe GDB is
using a 0 address for bad purposes internally).
-Play with RS/6000 shared libraries (using shared library tests
-listed in testsuite/TODO as a guide). (Schauer has done shared
-library stuff on most other platforms but has not touched the
-RS/6000).
-
-Make "info path" and path_comma work again (but independent of the
+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
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/core.c and gdb/core.c confused (this should be easy to
+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().
/foo/bar.c works whether compiled by cc /foo/bar.c, or cd /foo; cc
bar.c).
-merge xcoffexec.c and exec.c (might need a simple hook or two in
-exec.c, but that's no excuse to duplicate the whole thing). Merge
-xcoffread.c and coffread.c. Use breakpoint_re_set instead of
+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
Make a watchpoint which contains a function call an error (it is
broken now, making it work is probably not worth the effort).
-Make SIGINT handling independent of the debugging target. Do this
-by adding a new target_send_signal which sends a signal to a running
-process. (This is to replace the calls to signal() in remote.c).
+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
debugging servers and you want to dodge out and initiate a connection
to a server running under gdb.
-Work out and implement a reasonably general mechanism for multi-threaded
-processies. There are parts of one implemented in convex-dep.c, if
-you want an example.
-
Add stab information to allow reasonable debugging of inline functions
(possibly they should show up on a stack backtrace? With a note
indicating that they weren't "real"?).
-Implement support for specifying arbitrary locations of stack frames
-(in practice, this usually requires specification of both the top and
-bottom of the stack frame (fp and sp), since you *must* retrieve the
-pc that was saved in the innermost frame).
-
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
Modify gdb to work correctly with Pascal.
-Rewrite macros that handle frame chaining and frameless functions.
-They should be able to tell the difference between start, main, and a
-frameless function called from main.
-
-Work out what information would need to be included in an executable
-by the compiler to allow gdb to debug functions which do not have a
-frame pointer. Modify gdb and gcc to do this.
-
-When `attached' to a program (via either OS support or remote
-debugging), gdb should arrange to catch signals which the terminal
-might send, as it is unlikely that the program will be able to notice
-them. SIGINT and SIGTSTP are obvious examples.
-
-Arrange for list_command not to use decode_line_1 and thus not require
-symbols to be read in simply to read a source file.
-
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 / binutils.git / blobdiff