From: Jim Kingdon Date: Sun, 25 Sep 1994 13:21:22 +0000 (+0000) Subject: * TODO: Remove item about adding general multi-threaded stuff; X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=8cbe898dad45fa01dfa4d9803992d5d6ad73e883;p=binutils-gdb.git * TODO: Remove item about adding general multi-threaded stuff; this is done. Remove item about specifying arbitrary locations of stack frames (this works on some machines). Remove item about debugging functions without a frame pointer (this works on some machines). Remove item about re-writing macros which handle frame chaining and frameless functions. They have been re-written at least once since that item was written. Remove item about gdb catching SIGINT when attached; this is done. Remove item about having list_command not read symbols--why bother? --- diff --git a/gdb/TODO b/gdb/TODO index 093b8aeb967..a1ca339b173 100644 --- a/gdb/TODO +++ b/gdb/TODO @@ -443,19 +443,10 @@ 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. -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 @@ -475,22 +466,6 @@ more filtering. 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).