1 If you find inaccuracies in this list, please send mail to
2 gdb-patches@sourceware.cygnus.com. If you would like to work on any
3 of these, you should consider sending mail to the same address, to
4 find out whether anyone else is working on it.
7 Known problems in GDB 5.0
8 =========================
10 Below is a list of problems identified during the GDB 5.0 release
11 cycle. People hope to have these problems fixed in a follow-on
14 (The names in paren indicate people that posted the original problem.)
18 GDB doesn't build under IRIX6.4
22 Has anyone successfully built the latest (from cvs) gdb on IRIX6.4 or
23 later? The first problem I hit is that proc-api.c includes
24 sys/user.h, which no longer exists under IRIX6.4. If I comment out
25 that include, the next problem I hit is that PIOCGETPR and PIOCGETU
26 are no longer defined in IRIX6.4 (presumably related to the
27 disappearance of user.h).
31 The BFD directory requires bug-fixed AUTOMAKE et.al.
33 AUTOMAKE 1.4 incorrectly set the TEXINPUTS environment variable. It
34 contained the full path to texinfo.tex when it should have only
35 contained the directory. The bug has been fixed in the current
36 AUTOMAKE sources. Automake snapshots can be found in:
37 ftp://sourceware.cygnus.com/pub/gdb/snapshots
38 and ftp://sourceware.cygnus.com/pub/binutils
42 gdb-cvs fails to build on freebsd-elf
43 http://sourceware.cygnus.com/ml/gdb/2000-04/msg00004.html
45 Either the FreeBSD group need to contribute their local GDB changes
46 back to the master sources or someone needs to provides a new
47 (clean-room) implementation. Since the former involves a fairly
48 complicated assignment the latter may be easier. [cagney]
52 Generic: lin-thread cannot handle thread exit (Mark Kettenis, Michael
53 Snyder) http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00525.html
55 The thread_db assisted debugging code doesn't handle exiting threads
56 properly, at least in combination with glibc 2.1.3 (the framework is
57 there, just not the actual code). There are at least two problems
58 that prevent this from working.
60 As an additional reference point, the pre thread_db code did not work
65 Java (Anthony Green, David Taylor)
67 Anthony Green has a number of Java patches that did not make it into
71 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00512.html
74 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00515.html
76 Patch: handle N_MAIN stab
77 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00527.html
81 Pascal (Pierre Muller, David Taylor)
83 Pierre Muller has contributed patches for adding Pascal Language
86 2 pascal language patches inserted in database
87 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00521.html
90 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00496.html
94 GNU/Linux/x86 and random thread signals (and Solaris/SPARC but not
96 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00336.html
98 Christopher Blizzard writes:
100 So, I've done some more digging into this and it looks like Jim
101 Kingdon has reported this problem in the past:
103 http://sourceware.cygnus.com/ml/bug-gdb/1999-10/msg00058.html
105 I can reproduce this problem both with and without Tom's patch. Has
106 anyone seen this before? Maybe have a solution for it hanging around?
109 There's a test case for this documented at:
111 when debugging threaded applications you get extra SIGTRAPs
112 http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=9565
114 [There should be a GDB testcase - cagney]
118 Possible regressions with some devel GCCs.
119 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00475.html
121 gcc-2.95.2 outputs a line note *before* the prologue (and one for the
122 closing brace after the epilogue, instead of before it, as it used to
123 be). By disabling the RTL-style prologue generating mechanism
124 (undocumented GCC option -mno-schedule-prologue), you get back the
125 traditional behaviour.
126 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00510.html
128 This should now be fixed.
132 RFD: infrun.c: No bpstat_stop_status call after proceed over break?
134 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00665.html
136 GDB misses watchpoint triggers after proceeding over a breakpoint on
141 x86 linux GDB and SIGALRM (???)
142 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00803.html
144 I know there are problems with single stepping through signal
145 handlers. These problems were present in 4.18. They were just masked
146 because 4.18 failed to recognize signal handlers. Fixing it is not
147 easy, and will require changes to handle_inferior_event(), that I
148 prefer not to make before the 5.0 release.
154 Revised UDP support (was: Re: [Fwd: [patch] UDP transport support])
155 http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00000.html
157 (Broken) support for GDB's remote protocol across UDP is to be
158 included in the follow-on release.
162 Can't build IRIX -> arm GDB.
163 http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00356.html
166 > Now I'm building for an embedded arm target. If there is a way of turning
167 > remote-rdi off, I couldn't find it. It looks like it gets built by default
168 > in gdb/configure.tgt(line 58) Anyway, the build dies in
169 > gdb/rdi-share/unixcomm.c. SERPORT1 et. al. never get defined because we
170 > aren't one of the architectures supported.
174 Problem with weak functions
175 http://sourceware.cygnus.com/ml/gdb/2000-05/msg00060.html
177 Dan Nicolaescu writes:
178 > It seems that gdb-4.95.1 does not display correctly the function when
179 > stoping in weak functions.
181 > It stops in a function that is defined as weak, not in the function
182 > that is actualy run...
186 GDB5 TOT on unixware 7
187 http://sourceware.cygnus.com/ml/gdb/2000-04/msg00119.html
190 > I just spun the top of tree of the GDB5 branch on UnixWare 7. As a
191 > practical matter, the current thread support is somewhat more annoying
192 > than when GDB was thread-unaware.
199 The following are small cleanups that will hopefully be completed by
200 the follow on to 5.0.
206 The need for this as almost been eliminated. The next version of GCC
207 (assuming cagney gets the relevant patch committed) will be able to
208 supress unused parameter warnings.
212 Delete macro TARGET_BYTE_ORDER_SELECTABLE.
214 Patches in the database.
220 Readline 4.? is out. A merge wouldn't hurt.
226 Eliminate all uses of PARAMS in GDB's source code.
230 Elimination of make_cleanup_func. (Andrew Cagney)
232 make_cleanup_func elimination
233 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00791.html
234 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00814.html
238 Re: Various C++ things
240 value_headof/value_from_vtable_info are worthless, and should be removed.
241 The one place in printcmd.c that uses it should use the RTTI functions.
243 RTTI for g++ should be using the typeinfo functions rather than the vtables.
244 The typeinfo functions are always at offset 4 from the beginning of the vtable,
245 and are always right. The vtables will have weird names like E::VB sometimes.
246 The typeinfo function will always be "E type_info function", or somesuch.
248 value_virtual_fn_field needs to be fixed so there are no failures for virtual
249 functions for C++ using g++.
251 Testsuite cases are the major priority right now for C++ support, since i have
252 to make a lot of changes that could potentially break each other.
256 Fix ``set architecture <tab>''
258 This command should expand to a list of all supported architectures.
259 At present ``info architecture'' needs to be used. That is simply
260 wrong. It involves the use of add_set_enum_cmd().
264 GDBARCH cleanup (Andrew Cagney)
266 The non-generated parts of gdbarch.{sh,h,c} should be separated out
267 into arch-utils.[hc].
269 Document that gdbarch_init_ftype could easily fail because it didn't
270 identify an architecture.
274 Migrate qfThreadInfo packet -> qThreadInfo. (Andrew Cagney)
276 Add support for packet enable/disable commands with these thread
277 packets. General cleanup.
279 [PATCH] Document the ThreadInfo remote protocol queries
280 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00832.html
282 [PATCH] "info threads" queries for remote.c
283 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00831.html
287 General Cleanups / Fixes
288 ========================
290 The following are more general cleanups and fixes. They are not tied
291 to any specific release.
299 Eliminate gdb/tui/Makefile.in.
300 Cleanup configury support for optional sub-directories.
302 Check how GCC handles multiple front ends for an example of how things
303 could work. A tentative first step is to rationalize things so that
304 all sub directories are handled in a fashion similar to gdb/mi.
308 [PATCH/5] src/intl/Makefile.in:distclean additions
309 http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00363.html
311 Do not forget to merge the patch back into the trunk.
315 Update ALPHA so that it uses ``struct frame_extra_info'' instead of
318 This is a barrier to replacing mips_extra_func_info with something
319 that works with multi-arch.
323 Multi-arch mips_extra_func_info.
325 This first needs the alpha to be updated so that it uses ``struct
330 Send normal output to gdb_stdout.
331 Send error messages to gdb_stderror.
332 Send debug and log output log gdb_stdlog.
334 GDB still contains many cases where (f)printf or printf_filtered () is
335 used when it should be sending the messages to gdb_stderror or
340 Rationalize the host-endian code (grep for HOST_BYTE_ORDER).
342 At preent defs.h includes <endian.h> (which is linux specific) yet
343 almost nothing depends on it. Suggest "gdb_endian.h" which can also
344 handle <machine/endian.h> and only include that where it is really
349 Replace asprintf() calls with xasprintf() calls.
351 As with things like strdup() most calls to asprintf() don't check the
356 Rationaize savestring(), msavestring() and mstrsave().
358 In general libiberty's xstrdup () can be used.
362 Eliminate mmalloc() from GDB.
364 Also eliminate it from defs.h.
368 Check/cleanup MI documentation.
370 The list of commands specified in the documentation needs to be
371 checked against the mi-cmds.c table in a mechanical way (so that they
372 two can be kept up-to-date).
376 Eliminate error_begin().
378 With ui_file, there is no need for the statefull error_begin ()
383 Add built-by, build-date, tm, xm, nm and anything else into gdb binary
384 so that you can see how the GDB was created.
386 Some of these (*m.h) would be added to the generated config.h. That
387 in turn would fix a long standing bug where by the build process many
388 not notice a changed tm.h file. Since everything depends on config.h,
389 a change to *m.h forces a change to config.h and, consequently forces
394 Replace gdb_stdtarg with gdb_targout (and possibly gdb_targerr).
396 gdb_stdtarg is easily confused with gdb_stdarg.
400 Remote protocol doco feedback.
402 Too much feedback to mention needs to be merged in (901660). Search
403 for the word ``remote''.
407 set/show remote X-packet ...
409 ``(gdb) help set remote X-packet'' doesn't list the applicable
410 responses. The help message needs to be expanded.
414 Extra ui_file methods - dump.
416 These are for debugging / testing. An aside is to set up a whitebox
417 testsuite for key internals such as ui_file.
421 Add an "info bfd" command that displays supported object formats,
422 similarly to objdump -i.
424 Is there a command already?
428 Architectural Changes
429 =====================
431 These are harder than simple cleanups / fixes and, consequently
432 involve more work. Typically an Architectural Change will be broken
433 down into a more digestible set of cleanups and fixes.
437 Replace READ_FP() with FRAME_HANDLE().
439 READ_FP() is a hangover from the days of the vax when the ABI really
440 did have a frame pointer register. Modern architectures typically
441 construct a virtual frame-handle from the stack pointer and various
442 other bits of string.
444 Unfortunatly GDB still treats this synthetic FP register as though it
445 is real. That in turn really confuses users (arm and ``print $fp'' VS
446 ``info registers fp''). The synthetic FP should be separated out of
447 the true register set presented to the user.
451 MI's input does not use buffering.
453 At present the MI interface reads raw characters of from an unbuffered
454 FD. This is to avoid several nasty buffer/race conditions. That code
455 should be changed so that it registers its self with the event loop
456 (on the input FD) and then push commands up to MI as they arrive.
458 The serial code already does this.
462 Register Cache Cleanup (below from Andrew Cagney)
464 I would depict the current register architecture as something like:
471 register + REGISTER_BYTE(reg_nr)
474 -------------------------
475 | extern register[] |
476 -------------------------
478 where neither the high (valops.c et.al.) or low gdb (*-tdep.c) are
479 really clear on what mechanisms they should be using to manipulate that
480 buffer. Further, much code assumes, dangerously, that registers are
481 contigious. Having got mips-tdep.c to support multiple ABIs, believe
482 me, that is a bad assumption. Finally, that register cache layout is
483 determined by the current remote/local target and _not_ the less
484 specific target ISA. In fact, in many cases it is determined by the
485 somewhat arbitrary layout of the [gG] packets!
488 How I would like the register file to work is more like:
516 The main objectives being:
518 o a clear separation between the low
519 level target and the high level GDB
521 o a mechanism that solves the general
522 problem of register aliases, overlaps
523 etc instead of treating them as optional
524 extras that can be wedged in as an after
525 thought (that is a reasonable description
526 of the current code).
528 Identify then solve the hard case and the
529 rest just falls out. GDB solved the easy
530 case and then tried to ignore the real
533 o a removal of the assumption that the
534 mapping between the register cache
535 and virtual registers is largely static.
536 If you flip the USR/SSR stack register
537 select bit in the status-register then
538 the corresponding stack registers should
541 o a mechanism that clearly separates the
542 gdb internal register cache from any
543 target (not architecture) dependant
544 specifics such as [gG] packets.
546 Of course, like anything, it sounds good in theory. In reality, it
547 would have to contend with many<->many relationships at both the
548 virt<->cache and cache<->target level. For instance:
551 Modifying an mmx register may involve
552 scattering values across both FP and
553 mmpx specific parts of a buffer
556 When writing back a SP it may need to
557 both be written to both SP and USP.
562 Rather than let this like the last time it was discussed, just slip, I'm
563 first going to add this e-mail (+ references) to TODO. I'd then like to
564 sketch out a broad strategy I think could get us there.
567 First thing I'd suggest is separating out the ``extern registers[]''
568 code so that we can at least identify what is using it. At present
569 things are scattered across many files. That way we can at least
570 pretend that there is a cache instead of a global array :-)
572 I'd then suggest someone putting up a proposal for the pseudo-reg /
573 high-level side interface so that code can be adopted to it. For old
574 code, initially a blanket rename of write_register_bytes() to
575 deprecated_write_register_bytes() would help.
577 Following that would, finaly be the corresponding changes to the target.
581 Check that GDB can handle all BFD architectures (Andrew Cagney)
583 There should be a test that checks that BFD/GDB are in sync with
584 regard to architecture changes. Something like a test that first
585 queries GDB for all supported architectures and then feeds each back
586 to GDB.. Anyone interested in learning how to write tests? :-)
590 Add support for Modula3
592 Get DEC/Compaq to contribute their Modula-3 support.
596 Convert ALL architectures to MULTI-ARCH.
600 Convert GDB build process to AUTOMAKE.
604 Restructure gdb directory tree so that it avoids any 8.3 and 14
609 Can the xdep files be replaced by autoconf?
610 Can the tm.h and nm.h files be eliminated by multi-arch.
614 Add a transcript mechanism to GDB.
616 Such a mechanism might log all gdb input and output to a file in a
617 form that would allow it to be replayed. It could involve ``gdb
618 --transcript=FILE'' or it could involve ``(gdb) transcript file''.
622 Make MI interface accessable from existing CLI.
626 Select the initial multi-arch ISA / ABI based on --target or similar.
628 At present the default is based on what ever is first in the BFD
629 archures table. It should be determined based on the ``--target=...''
636 Enable the code to recognize --enable-targets=.... like BINUTILS does.
640 Add a breakpoint-edit command to MI.
642 It would be similar to MI's breakpoint create but would apply to an
643 existing breakpoint. It saves the need to delete/create breakpoints
644 when ever they are changed.
648 Add directory path to MI breakpoint.
650 That way the GUI's task of finding the file within which the
651 breakpoint was set is simplified.
655 Re-do GDB's output pager.
657 GDB's output pager still relies on people correctly using *_filtered
658 for gdb_stdout and *_unfiltered for gdb_stdlog / gdb_stderr.
659 Hopefully, with all normal output going to gdb_stdout, the pager can
660 just look at the ui_file that the output is on and then use that to
661 decide what to do about paging. Sounds good in theory.
665 Add mechanism to reject expression classes to MI
667 There are situtations where you don't want GDB's expression
668 parser/evaluator to perform inferior function calls or variable
673 Remove sideffects from libgdb breakpoint create function.
675 The user can use the CLI to create a breakpoint with partial
676 information - no file (gdb would use the file from the last
679 The libgdb interface currently affects that environment which can lead
680 to confusion when a user is setting breakpoints via both the MI and
683 This is also a good example of how getting the CLI ``right'' will be
688 GDB doesn't recover gracefully from remote protocol errors.
690 GDB wasn't checking for NAKs from the remote target. Instead a NAK is
691 ignored and a timeout is required before GDB retries. A pre-cursor to
692 fixing this this is making GDB's remote protocol packet more robust.
694 While downloading to a remote protocol target, gdb ignores packet
695 errors in so far as it will continue to edownload with chunk N+1 even
696 if chunk N was not correctly sent. This causes gdb.base/remote.exp to
697 take a painfully long time to run. As a PS that test needs to be
698 fixed so that it builds on 16 bit machines.
702 Move gdb_lasterr to ui_out?
704 The way GDB throws errors and records them needs a re-think. ui_out
705 handles the correct output well. It doesn't resolve what to do with
706 output / error-messages when things go wrong.
710 Fix implementation of ``target xxx''.
712 At present when the user specifies ``target xxxx'', the CLI maps that
713 directly onto a target open method. It is then assumed that the
714 target open method should do all sorts of complicated things as this
715 is the only chance it has. Check how the various remote targets
716 duplicate the target operations. Check also how the various targets
717 behave differently for purely arbitrary reasons.
719 What should happen is that ``target xxxx'' should call a generic
720 ``target'' function and that should then co-ordinate the opening of
721 ``xxxx''. This becomes especially important when you're trying to
722 open an asynchronous target that may need to perform background tasks
723 as part of the ``attach'' phase.
725 Unfortunatly, due to limitations in the old/creaking command.h
726 interface, that isn't possible. The function being called isn't told
727 of the ``xxx'' or any other context information.
729 Consequently a precursor to fixing ``target xxxx'' is to clean up the
730 CLI code so that it passes to the callback function (attatched to a
731 command) useful information such as the actual command and a context
732 for that command. Other changes such as making ``struct command''
733 opaque may also help.
737 Document trace machinery
741 Document overlay machinery.
748 This list is not up to date, and opinions vary about the importance or
749 even desirability of some of the items. If you do fix something, it
750 always pays to check the below.
754 @c This does not work (yet if ever). FIXME.
755 @c @item --parse=@var{lang} @dots{}
756 @c Configure the @value{GDBN} expression parser to parse the listed languages.
757 @c @samp{all} configures @value{GDBN} for all supported languages. To get a
758 @c list of all supported languages, omit the argument. Without this
759 @c option, @value{GDBN} is configured to parse all supported languages.
763 START_INFERIOR_TRAPS_EXPECTED need never be defined to 2, since that
764 is its default value. Clean this up.
768 It should be possible to use symbols from shared libraries before we know
769 exactly where the libraries will be loaded. E.g. "b perror" before running
770 the program. This could maybe be done as an extension of the "breakpoint
771 re-evaluation" after new symbols are loaded.
775 Make single_step() insert and remove breakpoints in one operation.
779 Speed up single stepping by avoiding extraneous ptrace calls.
783 Speed up single stepping by not inserting and removing breakpoints
784 each time the inferior starts and stops.
786 Breakpoints should not be inserted and deleted all the time. Only the
787 one(s) there should be removed when we have to step over one. Support
788 breakpoints that don't have to be removed to step over them.
790 [this has resulted in numerous debates. The issue isn't clear cut]
794 Provide "voodoo" debugging of core files. This creates a zombie
795 process as a child of the debugger, and loads it up with the data,
796 stack, and regs of the core file. This allows you to call functions
797 in the executable, to manipulate the data in the core file.
803 GDB reopens the source file on every line, as you "next" through it.
805 [still true? I've a memory of this being fixed]
809 Perhaps "i source" should take an argument like that of "list".
813 Remove "at 0xnnnn" from the "b foo" response, if `print address off' and if
814 it matches the source line indicated.
818 The prompt at end of screen should accept space as well as CR.
822 Backtrace should point out what the currently selected frame is, in
823 its display, perhaps showing "@3 foo (bar, ...)" or ">3 foo (bar,
824 ...)" rather than "#3 foo (bar, ...)".
828 "i program" should work for core files, and display more info, like what
829 actually caused it to die.
833 "x/10i" should shorten the long name, if any, on subsequent lines.
837 "next" over a function that longjumps, never stops until next time you happen
838 to get to that spot by accident. E.g. "n" over execute_command which has
843 "set zeroprint off", don't bother printing members of structs which
844 are entirely zero. Useful for those big structs with few useful
849 GDB does four ioctl's for every command, probably switching terminal modes
850 to/from inferior or for readline or something.
854 terminal_ours versus terminal_inferior: cache state. Switch should be a noop
855 if the state is the same, too.
859 "i frame" shows wrong "arglist at" location, doesn't show where the args
860 should be found, only their actual values.
864 There should be a way for "set" commands to validate the new setting
865 before it takes effect.
869 "ena d" is ambiguous, why? "ena delete" seems to think it is a command!
873 i line VAR produces "Line number not known for symbol ``var''.". I
874 thought we were stashing that info now!
878 We should be able to write to random files at hex offsets like adb.
882 Make "target xxx" command interruptible.
886 [elena - delete this]
888 Handle add_file with separate text, data, and bss addresses. Maybe
889 handle separate addresses for each segment in the object file?
893 [Jimb/Elena delete this one]
895 Handle free_named_symtab to cope with multiply-loaded object files
896 in a dynamic linking environment. Should remember the last copy loaded,
897 but not get too snowed if it finds references to the older copy.
901 [elena delete this also]
903 Remove all references to:
910 now that we have BFD. All remaining are in machine dependent files.
914 Re-organize help categories into things that tend to fit on a screen
919 Add in commands like ADB's for searching for patterns, etc. We should
920 be able to examine and patch raw unsymboled binaries as well in gdb as
921 we can in adb. (E.g. increase the timeout in /bin/login without source).
923 [actually, add ADB interface :-]
927 When doing "step" or "next", if a few lines of source are skipped between
928 the previous line and the current one, print those lines, not just the
929 last line of a multiline statement.
933 Handling of "&" address-of operator needs some serious overhaul
934 for ANSI C and consistency on arrays and functions.
935 For "float point[15];":
936 ptype &point[4] ==> Attempt to take address of non-lvalue.
937 For "char *malloc();":
938 ptype malloc ==> "char *()"; should be same as
939 ptype &malloc ==> "char *(*)()"
940 call printf ("%x\n", malloc) ==> weird value, should be same as
941 call printf ("%x\n", &malloc) ==> correct value
945 Fix dbxread.c symbol reading in the presence of interrupts. It
946 currently leaves a cleanup to blow away the entire symbol table when a
947 QUIT occurs. (What's wrong with that? -kingdon, 28 Oct 1993).
949 [I suspect that the grype was that, on a slow system, you might want
950 to cntrl-c and get just half the symbols and then load the rest later
951 - scary to be honest]
955 Mipsread.c reads include files depth-first, because the dependencies
956 in the psymtabs are way too inclusive (it seems to me). Figure out what
957 really depends on what, to avoid recursing 20 or 30 times while reading
962 value_add() should be subtracting the lower bound of arrays, if known,
963 and possibly checking against the upper bound for error reporting.
967 When listing source lines, check for a preceding \n, to verify that
968 the file hasn't changed out from under us.
970 [fixed by some other means I think. That hack wouldn't actually work
971 reliably - the file might move such that another \n appears. ]
975 Get all the remote systems (where the protocol allows it) to be able to
976 stop the remote system when the GDB user types ^C (like remote.c
977 does). For ebmon, use ^Ak.
981 Possible feature: A version of the "disassemble" command which shows
982 both source and assembly code ("set symbol-filename on" is a partial
985 [has this been done? It was certainly done for MI and GDBtk]
989 investigate "x/s 0" (right now stops early) (I think maybe GDB is
990 using a 0 address for bad purposes internally).
994 Make "info path" and path_command work again (but independent of the
995 environment either of gdb or that we'll pass to the inferior).
999 Make GDB understand the GCC feature for putting octal constants in
1000 enums. Make it so overflow on an enum constant does not error_type
1001 the whole type. Allow arbitrarily large enums with type attributes.
1002 Put all this stuff in the testsuite.
1006 Make TYPE_CODE_ERROR with a non-zero TYPE_LENGTH more useful (print
1007 the value in hex; process type attributes). Add this to the
1008 testsuite. This way future compilers can add new types and old
1009 versions of GDB can do something halfway reasonable.
1013 Fix mdebugread.c:parse_type to do fundamental types right (see
1014 rs6000_builtin_type in stabsread.c for what "right" is--the point is
1015 that the debug format fixes the sizes of these things and it shouldn't
1016 depend on stuff like TARGET_PTR_BIT and so on. For mdebug, there seem
1017 to be separate bt* codes for 64 bit and 32 bit things, and GDB should
1018 be aware of that). Also use a switch statement for clarity and speed.
1022 Investigate adding symbols in target_load--some targets do, some
1027 Put dirname in psymtabs and change lookup*symtab to use dirname (so
1028 /foo/bar.c works whether compiled by cc /foo/bar.c, or cd /foo; cc
1033 Merge xcoffread.c and coffread.c. Use breakpoint_re_set instead of
1038 Make a watchpoint which contains a function call an error (it is
1039 broken now, making it work is probably not worth the effort).
1043 New test case based on weird.exp but in which type numbers are not
1044 renumbered (thus multiply defining a type). This currently causes an
1045 infinite loop on "p v_comb".
1049 [Hey! Hint Hint Delete Delete!!!]
1051 Fix 386 floating point so that floating point registers are real
1052 registers (but code can deal at run-time if they are missing, like
1053 mips and 68k). This would clean up "info float" and related stuff.
1057 gcc -g -c enummask.c then gdb enummask.o, then "p v". GDB complains
1058 about not being able to access memory location 0.
1060 -------------------- enummask.c
1081 If try to modify value in file with "set write off" should give
1082 appropriate error not "cannot access memory at address 0x65e0".
1086 Allow core file without exec file on RS/6000.
1090 Make sure "shell" with no arguments works right on DOS.
1094 Make gdb.ini (as well as .gdbinit) be checked on all platforms, so
1095 the same directory can be NFS-mounted on unix or DOS, and work the
1100 [Is this another delete???]
1102 Get SECT_OFF_TEXT stuff out of objfile_relocate (might be needed to
1103 get RS/6000 to work right, might not be immediately relevant).
1107 Work out some kind of way to allow running the inferior to be done as
1108 a sub-execution of, eg. breakpoint command lists. Currently running
1109 the inferior interupts any command list execution. This would require
1110 some rewriting of wait_for_inferior & friends, and hence should
1111 probably be done in concert with the above.
1115 Add function arguments to gdb user defined functions.
1119 Add convenience variables that refer to exec file, symbol file,
1120 selected frame source file, selected frame function, selected frame
1125 Add a "suspend" subcommand of the "continue" command to suspend gdb
1126 while continuing execution of the subprocess. Useful when you are
1127 debugging servers and you want to dodge out and initiate a connection
1128 to a server running under gdb.
1134 Modify the handling of symbols grouped through BINCL/EINCL stabs to
1135 allocate a partial symtab for each BINCL/EINCL grouping. This will
1136 seriously decrease the size of inter-psymtab dependencies and hence
1137 lessen the amount that needs to be read in when a new source file is
1144 Modify gdb to work correctly with Pascal.
1148 Add a command for searching memory, a la adb. It specifies size,
1149 mask, value, start address. ADB searches until it finds it or hits
1150 an error (or is interrupted).
1154 Remove the range and type checking code and documentation, if not