2003-06-23 Elena Zannoni <ezannoni@redhat.com>

[deliverable/binutils-gdb.git] / gdb / testsuite / TODO

diff --git a/gdb/testsuite/TODO b/gdb/testsuite/TODO
index abb0f32c97ed2e927477b3420e0778abd92e6ce4..978991c77cdb0f936497856fa2ace5f5502db457 100644 (file)
--- a/gdb/testsuite/TODO
+++ b/gdb/testsuite/TODO
@@ -5,7 +5,10 @@ reliably without unexpected failures on the "standard" machines, etc.
 This list exists largely as "tests we can add when we are ready to
 risk destabilizing it again".
 
-nodebug.exp--test printing variables.
+There are some tests which are only run on some platforms because they
+have not been tested on more platforms.  Enable them and fix any
+problems.  A partial list: recurse.exp, watchpoint.exp
+(test_watchpoint_triggered_in_syscall, test_complex_watchpoint).
 
 Test printing of structures passed by value, for the 7th, 8th, and 9th
 arguments (PR 1714).  Test printing structure arguments of
@@ -15,13 +18,7 @@ sizes ("return", "finish", and call function).
 Get crossload tests to use --enable-targets and reenable them.
 
 corefile.exp:
-1.  Print variables from the core file (data and stack), and text
-(from the exec file).  This tests whether the corefile sections are
-mapped to the right addresses.
-2.  Test what happens when we get a new exec file without explicitly
-getting rid of the core file (we at least must avoid core dumps and such).
-3.  Test backtrace in corefile.exp.
-4.  Test ability to run program when there is a core target, then go
+Test ability to run program when there is a core target, then go
 back to the core file when the program exits.
 
 Test handling of floating point variables
@@ -36,8 +33,9 @@ appropriately (integer registers in decimal, registers which always
 contain addresses (pc, probably sp and fp, maybe others) in hex,
 floating point).
 
-Test completer.  There is a list of test cases in main.c in the gdb
-source.  Test these with TAB, M-?, and the "complete" command.
+Test completer.  Test that it completes a variety of things correctly
+(see the list of test cases in main.c in the gdb source).  Test TAB,
+M-?, and the "complete" command.
 
 Test "info line" with all kinds of linespecs.  Test that the last line
 of the file works right.
@@ -61,6 +59,11 @@ Test printing complicated types, including functions, pointers to
 arrays of pointers of functions, functions which return pointers to
 functions, etc.
 
+printcmd.exp--test printing enum values.  Test printing an enum
+variable whose value is out of range.  Test "p (int)enum_var", "p/x
+enum_var".  Test that in something like "enum {FOO, LAST_THING=FOO}"
+we print FOO, not LAST_THING.
+
 Test GDB expressions--test all operators (and overloaded operators for
 C++).  Test integer constants which are signed or unsigned int, long,
 or long long.  Test detection of overflow of an integer constant.
@@ -81,9 +84,6 @@ an inferior each of these ways (to test that inflow.c works).  Test
 that GDB works if the last line of stdin or a source'd file lacks a
 newline.
 
-Test that module__2do (for example) in a C program does not get
-demangled.
-
 Test that unmatched single quotes produce error messages, both in
 expressions and linespecs.
 
@@ -183,9 +183,10 @@ compiler dependencies.
 Test more obscure wait_for_inferior cases, expanding on the tests in
 watchpoint.exp, signals.exp, etc.
 
-Test that the copyright year in the startup message matches the
-current year (would produce a single spurious FAIL on old GDB's, but
-probably still a good idea).
+Test stepping into functions which are one line long and functions
+which are on line 1 of the source file. (there is a class of bugs in
+which gdb doesn't find the line number information, and thus doesn't
+step into the function).
 
 Test that prologue recognition, backtrace, printing locals, etc.,
 still work in the presence of large frames (the point being that at