espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-06-27 14:39:09 +08:00
Code Issues Packages Projects Releases Wiki Activity

* TODO: Remove item about adding general multi-threaded stuff;

Browse Source 
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?
This commit is contained in:
Jim Kingdon
1994-09-25 13:21:22 +00:00
parent 718bccf167
commit 8cbe898dad
1 changed files with 0 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
gdb/TODO
View File

@ -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 debugging servers and you want to dodge out and initiate a connection
to a server running under gdb. 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 Add stab information to allow reasonable debugging of inline functions
(possibly they should show up on a stack backtrace? With a note (possibly they should show up on a stack backtrace? With a note
indicating that they weren't "real"?). 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 Modify the naked "until" command to step until past the current source
line, rather than past the current pc value. This is tricky simply 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 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. 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, Add a command for searching memory, a la adb. It specifies size,
mask, value, start address. ADB searches until it finds it or hits mask, value, start address. ADB searches until it finds it or hits
an error (or is interrupted). an error (or is interrupted).