you should consider sending mail to the same address, to find out
whether anyone else is working on it.
-General To Do List
-------------------
+
+Known problems in GDB 5.0
+=========================
+
+Below is a list of problems identified during the GDB 5.0 release
+cycle. People hope to have these problems fixed in a follow-on
+release.
+
+(The names in paren indicate people that posted the original problem.)
+
+--
+
+GDB doesn't build under IRIX6.4
+
+Benjamin Gamsa wrote:
+
+Has anyone successfully built the latest (from cvs) gdb on IRIX6.4 or
+later? The first problem I hit is that proc-api.c includes
+sys/user.h, which no longer exists under IRIX6.4. If I comment out
+that include, the next problem I hit is that PIOCGETPR and PIOCGETU
+are no longer defined in IRIX6.4 (presumably related to the
+disappearance of user.h).
+
+--
+
+gdb-cvs fails to build on freebsd-elf
+http://sourceware.cygnus.com/ml/gdb/2000-04/msg00004.html
+
+Either the FreeBSD group need to contribute their local GDB changes
+back to the master sources or someone needs to provides a new
+(clean-room) implementation. Since the former involves a fairly
+complicated assignment the latter may be easier. [cagney]
+
+--
+
+Generic: lin-thread cannot handle thread exit (Mark Kettenis, Michael
+Snyder) http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00525.html
+
+The thread_db assisted debugging code doesn't handle exiting threads
+properly, at least in combination with glibc 2.1.3 (the framework is
+there, just not the actual code). There are at least two problems
+that prevent this from working.
+
+As an additional reference point, the pre thread_db code did not work
+either.
+
+--
+
+Java (Anthony Green, David Taylor)
+
+Anthony Green has a number of Java patches that did not make it into
+the 5.0 release.
+
+Patch: java tests
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00512.html
+
+Patch: java booleans
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00515.html
+
+Patch: handle N_MAIN stab
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00527.html
+
+--
+
+Pascal (Pierre Muller, David Taylor)
+
+Pierre Muller has contributed patches for adding Pascal Language
+support to GDB.
+
+2 pascal language patches inserted in database
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00521.html
+
+Indent -gnu ?
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00496.html
+
+--
+
+GNU/Linux/x86 and random thread signals (and Solaris/SPARC but not
+Solaris/x86).
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00336.html
+
+Christopher Blizzard writes:
+
+So, I've done some more digging into this and it looks like Jim
+Kingdon has reported this problem in the past:
+
+http://sourceware.cygnus.com/ml/bug-gdb/1999-10/msg00058.html
+
+I can reproduce this problem both with and without Tom's patch. Has
+anyone seen this before? Maybe have a solution for it hanging around?
+:)
+
+There's a test case for this documented at:
+
+when debugging threaded applications you get extra SIGTRAPs
+http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=9565
+
+[There should be a GDB testcase - cagney]
+
+--
+
+Possible regressions with some devel GCCs.
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00475.html
+
+gcc-2.95.2 outputs a line note *before* the prologue (and one for the
+closing brace after the epilogue, instead of before it, as it used to
+be). By disabling the RTL-style prologue generating mechanism
+(undocumented GCC option -mno-schedule-prologue), you get back the
+traditional behaviour.
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00510.html
+
+This should now be fixed.
+
+--
+
+RFD: infrun.c: No bpstat_stop_status call after proceed over break?
+(Peter Schauer)
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00665.html
+
+GDB misses watchpoint triggers after proceeding over a breakpoint on
+x86 targets.
+
+--
+
+x86 linux GDB and SIGALRM (???)
+http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00803.html
+
+I know there are problems with single stepping through signal
+handlers. These problems were present in 4.18. They were just masked
+because 4.18 failed to recognize signal handlers. Fixing it is not
+easy, and will require changes to handle_inferior_event(), that I
+prefer not to make before the 5.0 release.
+
+Mark
+
+--
+
+Revised UDP support (was: Re: [Fwd: [patch] UDP transport support])
+http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00000.html
+
+(Broken) support for GDB's remote protocol across UDP is to be
+included in the follow-on release.
+
+--
+
+ ------------------------------------------------
+
+Code cleanups
+=============
+
+The following code cleanups are planned for the follow-on release to
+GDB 5.0.
+
+--
+
+ATTRIBUTE_UNUSED
+
+The need for this as almost been eliminated. The next version of GCC
+(assuming cagney gets the relevant patch committed) will be able to
+supress unused parameter warnings.
+
+--
+
+Delete macro TARGET_BYTE_ORDER_SELECTABLE.
+
+Patches in the database.
+
+--
+
+Updated readline
+
+Readline 4.? is out. A merge wouldn't hurt.
+
+--
+
+Purge PARAMS
+
+Eliminate all uses of PARAMS in GDB's source code.
+
+--
+
+Elimination of make_cleanup_func. (Andrew Cagney)
+
+make_cleanup_func elimination
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00791.html
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00814.html
+
+--
+
+ChangeLog.mi vs ChangeLog-mi (Andrew Cagney)
+Needs further debate.
+
+Re: [PATCH] Add change-log variables to more MI files
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00811.html
+
+--
+
+Re: Various C++ things
+
+value_headof/value_from_vtable_info are worthless, and should be removed.
+The one place in printcmd.c that uses it should use the RTTI functions.
+
+RTTI for g++ should be using the typeinfo functions rather than the vtables.
+The typeinfo functions are always at offset 4 from the beginning of the vtable,
+and are always right. The vtables will have weird names like E::VB sometimes.
+The typeinfo function will always be "E type_info function", or somesuch.
+
+value_virtual_fn_field needs to be fixed so there are no failures for virtual
+functions for C++ using g++.
+
+Testsuite cases are the major priority right now for C++ support, since i have
+to make a lot of changes that could potentially break each other.
+
+--
+
+GDBARCH cleanup (Andrew Cagney)
+
+The non-generated parts of gdbarch.{sh,h,c} should be separated out
+into arch-utils.[hc].
+
+The ``info architecture'' command should be replaced with a fixed
+``set architecture'' (implemented using the command.c enum code).
+
+Document that gdbarch_init_ftype could easily fail because it didn't
+identify an architecture.
+
+--
+
+Migrate qfThreadInfo packet -> qThreadInfo. (Andrew Cagney)
+
+Add support for packet enable/disable commands with these thread
+packets. General cleanup.
+
+[PATCH] Document the ThreadInfo remote protocol queries
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00832.html
+
+[PATCH] "info threads" queries for remote.c
+http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00831.html
+
+--
+
+Eliminate gdb/tui/Makefile.in.
+Cleanup configury support for optional sub-directories.
+
+Check how GCC handles multiple front ends for an example of how things
+could work. A tentative first step is to rationalize things so that
+all sub directories are handled in a fashion similar to gdb/mi.
+
+--
+
+[PATCH/5] src/intl/Makefile.in:distclean additions
+http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00363.html
+
+Do not forget to merge the patch back into the trunk.
+
+--
+
+Re: [RFC] Change configure.in so -W arnings match reality
+http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00350.html
+
+Some GCC compilers do not like -Wreturn-type. (Going forward there
+may be more problems like that). Need to check which of the warning
+options are valid. Need to probably disable warnings by default.
+
+--
+
+General Wish List
+=================
+
+--
+
+Check that GDB can handle all BFD architectures (Andrew Cagney)
+
+There should be a test that checks that BFD/GDB are in sync with
+regard to architecture changes. Something like a test that first
+queries GDB for all supported architectures and then feeds each back
+to GDB.. Anyone interested in learning how to write tests? :-)
+
+--
This list is probably not up to date, and opinions vary about the
importance or even desirability of some of the items.
+Document trace machinery.
+
+Document overlay machinery.
+
+Extend .gdbinit mechanism to specify name on command line, allow for
+lists of files to load, include function of --tclcommand.
+
+@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.
+
+Add an "info bfd" command that displays supported object formats,
+similarly to objdump -i.
+
START_INFERIOR_TRAPS_EXPECTED need never be defined to 2, since that
is its default value. Clean this up.
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
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().
in tm-z8k.h)? I thought the standard register names were supposed to
be just that, standard.
-Make DEBUG_EXPRESSIONS a maintenance command, dependent on
-MAINTENANCE_COMMANDS.
-
Allow core file without exec file on RS/6000.
Make sure "shell" with no arguments works right on DOS.
mask, value, start address. ADB searches until it finds it or hits
an error (or is interrupted).
-The GDB_TARGET_IS_HPPA kludges in partial-stab.h should be zapped sometime
-after GCC-2.7 has been released (whenever we decide corner case debugging
-problems with GCC-2.6 compiled code are not important).
+Remove the range and type checking code and documentation, if not
+going to implement.
# Local Variables:
# mode: text
projects / deliverable / binutils-gdb.git / blobdiff