1 If you find inaccuracies in this list, please send mail to
2 bug-gdb@prep.ai.mit.edu. If you would like to work on any of these,
3 you should consider sending mail to the same address, to find out
4 whether anyone else is working on it.
10 Here are _all_ the issues that have been raised vis-a-vis the 5.0
11 release. Also check the GDB, and other, mail archives
12 (http://sourceware.cygnus.com/ml/gdb/).
14 If, however, you fix something, then feel free to tweek this file
15 (deleting the problem). Just send a note to gdb-patches so that I see
18 The names in paren are those that might know more about the problem.
19 They don't necessarily indicate the people that will fix the problem.
26 These are things that have been identifed as must-have for this
31 Solaris/x86 - which? (Nick Duffek, Peter Schauer, Michael Snyder?)
33 Nick D's working through patches from Michael Snyder and Peter S.
38 RFA: procfs.c: init_procfs_ops should set
39 procfs_ops.to_has_[all]_memory (Peter Schauer, Andrew Cagney?)
41 I am pretty sure that this is caused by some accidental deletion, but
42 procfs.c:init_procfs_ops no longer sets procfs_ops.to_has_memory and
43 procfs_ops.to_has_all_memory.
45 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg01057.html
52 These are things that might make it in 5.0 but don't sit in the
53 critical path. If they miss the 5.0 cut then they definitly should
54 make the follow-on release.
58 Generic: lin-thread cannot handle thread exit (Mark Kettenis, Michael Snyder)
59 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00525.html
61 The thread_db assisted debugging code doesn't handle exiting threads
62 properly, at least in combination with glibc 2.1.3 (the framework is
63 there, just not the actual code). There are at least two problems
64 that prevent this from working.
66 As an additional reference point, the pre thread_db code didn't work
71 Java (Anthony Green, David Taylor)
73 Anthony Green has started contributing late breaking Java patches:
76 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00512.html
79 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00515.html
81 Patch: handle N_MAIN stab
82 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00527.html
84 It should be able to squeeze these in.
88 Pascal (Pierre Muller, David Taylor)
90 The pascal support patches nave been added to the patch data base. I
91 [cagney] strongly suspect that they are better suited for 5.1.
94 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00496.html
96 2 pascal language patches inserted in database
97 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00521.html
101 Programs run under GDB have SIGCHLD masked.
103 [I think this can be worked around by using the action command -
108 GNU/Linux/x86 and random thread signals (and Solaris/SPARC but not
111 Christopher Blizzard writes:
113 So, I've done some more digging into this and it looks like Jim
114 Kingdon has reported this problem in the past:
116 http://sourceware.cygnus.com/ml/bug-gdb/1999-10/msg00058.html
118 I can reproduce this problem both with and without Tom's patch. Has
119 anyone seen this before? Maybe have a solution for it hanging around?
122 There's a test case for this documented at:
124 when debugging threaded applications you get extra SIGTRAPs
125 http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=9565
127 [There should be a GDB testcase - cagney]
133 Benjamin Gamsa wrote:
135 Has anyone successfully built the latest (from cvs) gdb on IRIX6.4 or
136 later? The first problem I hit is that proc-api.c includes
137 sys/user.h, which no longer exists under IRIX6.4. If I comment out
138 that include, the next problem I hit is that PIOCGETPR and PIOCGETU
139 are no longer defined in IRIX6.4 (presumably related to the
140 disappearance of user.h).
144 Regressions (prologue) with devel GCC.
146 The current head of the GCC branch doesn't co-operate well with GDB
147 over debug information.
149 Regressions problem (200 failures)
150 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00475.html
154 RFA: infrun.c, breakpoint.c: Kludge for Solaris x86 hardware watchpoint support
155 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00664.html
157 Unfortunately I'd need the following kludge to work around a Solaris
158 x86 kernel problem with hardware watchpoint support. See the comment
159 in the patches for a description of the problem.
163 RFD: infrun.c: No bpstat_stop_status call after proceed over break ?
164 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00665.html
166 I am currently trying to fix a GDB bug with missing watchpoint triggers
167 after proceeding over a breakpoint on x86 targets.
171 x86 linux GDB and SIGALRM (???)
172 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00803.html
176 Migrate qfThreadInfo packet -> qThreadInfo. (Andrew Cagney)
178 Add support for packet enable/disable commands with these thread
179 packets. General cleanup.
181 [PATCH] Document the ThreadInfo remote protocol queries
182 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00832.html
184 [PATCH] "info threads" queries for remote.c
185 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00831.html
189 MI documentation in GDB user guide. (Andrew Cagney, Elena Zannoni,
190 Stan Shebs, anyone else?)
192 > (Are there plans to make gdbmi.texi be part of the manual as well?)
194 I'd like to see it go in there sooner rather than later too. Otherwise
195 you're introducing discrepancies between the manual and the documentation,
196 and everybody is confused - witness the lack of doc for the tracing
197 commands still, some two years after they were added...
199 Discussion on MI can be found on the thread: [PATCH] GDB command-line
200 switches and annotations docs
201 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00639.html
205 Revised UDP support (was: Re: [Fwd: [patch] UDP transport support])
206 http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00000.html
210 problems loading shared libraries - with attached test case
211 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00820.html
213 Hi, I'm having problems loading shared libraries. This is with a
214 build of gdb out of cvs that I pulled and built on March 27th and has
215 been there for at least a week. I haven't gone back further than
216 that. This is with the gcc that is shipping with Red Hat 6.2:
219 /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs gcc version
220 egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
222 I'm using "set auto-solib-add 0" after main has been called. If I use
223 "shar" to load a shared library manually once I can't use it again to
224 load another shared library later. Please see the attached log for an
225 example of how to reproduce the problem.
232 The following are on hold until GDB 5.0 is branched. In general they
233 won't go in as they unsettle the GDB sources.
239 The need for this as almost been eliminated. The next version of GCC
240 (assuming cagney gets the revised patch approved) will be able to
241 supress unused parameter warnings.
245 Delete macro TARGET_BYTE_ORDER_SELECTABLE.
247 Patches in the database.
253 Readline 4.? is out. A merge wouldn't hurt.
259 Something to do post 5.0 branch
263 Elimination of make_cleanup_func. (Andrew Cagney)
265 make_cleanup_func elimination
266 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00791.html
267 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00814.html
271 Allow GDB to use installed regex. Think about updating regex to more
272 recent version (Andrew Cagney).
274 Re: A new patch for regex
275 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00635.html
277 A patch for gnu-regex
278 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00568.html
282 ChangeLog.mi vs ChangeLog-mi (Andrew Cagney)
283 Needs further debate.
285 Re: [PATCH] Add change-log variables to more MI files
286 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00811.html
290 Re: gdb-cvs fails on freebsd-elf
291 http://sourceware.cygnus.com/ml/gdb/2000-04/msg00004.html
293 FreeBSD haven't contributed their local GDB changes back to the master
294 sources (they would at least need an FSF assignment by all
295 individuales that contributed to the work). Given the strong
296 likelhood that this will never happen, I'd suggest that a better
297 strategy would be for someone (with an FSF/GDD assignment) to do a new
298 (clean-room) implementation. That can then be accepted in time for
303 GDB 5.0: Test results
304 ---------------------
308 o the output of `config.guess`
311 o a note mentioning the reason
312 for any serious failures.
316 alpha-dec-osf4.0a, vendor compiler, 2000-03-04
318 Still has many compile warnings (mostly relating back to PTR vs void*)
319 but it did compile using:
326 # of expected passes 6223
327 # of unexpected failures 103
328 # of unexpected successes 2
329 # of expected failures 196
330 # of unresolved testcases 6
331 # of unsupported tests 1
333 Looking at the output it would appear that GDB is stepping into some
334 functions instead of ``next'' ing over them:
338 dummy () at /home/cagney/GDB-DEJAGNU/src/gdb/testsuite/gdb.base/all-types.c:41
341 Since there is no active maintainer, I'd consider this sufficient for
346 sparc-sun-solaris2.6, egcs-2.91.66, 2000-02-10
347 http://sourceware.cygnus.com/ml/gdb-testers/2000-q1/msg00030.html
349 There is a SIGTRAP problem that occures in ptrace.exp (Cagney to
352 # of expected passes 6420
353 # of unexpected failures 7
354 # of expected failures 199
358 solaris 2.5.1 sparc?, 2.9-gnupro-99r1, 2000-02-10
359 http://sourceware.cygnus.com/ml/gdb-testers/2000-q1/msg00032.html
361 # of expected passes 6420
362 # of unexpected failures 6
363 # of expected failures 199
367 sparc-unknown-netbsdelf1.4P, egcs-1.1.2+, 2000-03-01
369 This is with a very recent kernel.
371 # of expected passes 6055
372 # of unexpected failures 88
373 # of unexpected successes 1
374 # of expected failures 190
375 # of unresolved testcases 59
380 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00185.html
382 Kevins merged it all in.
388 Builds ok. Problems with some of the thread code. Unfortunate but
389 not a show stopper. Nick D's still looking at it.
391 Re: uw-threads issues
392 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00025.html
395 ------------------------------------------------
403 GDBARCH cleanup (Andrew Cagney)
405 The non-generated parts of gdbarch.{sh,h,c} should be separated out
406 into gdbarch-utils.[hc] (Name ok).
408 The ``info architecture'' command should be replaced with a fixed
409 ``set architecture'' (implemented using the command.c enum code).
411 Document that gdbarch_init_ftype could easily fail because it didn't
412 identify an architecture.
416 Check that GDB can handle all BFD architectures (Andrew Cagney)
418 There should be a test that checks that BFD/GDB are in sync with
419 regard to architecture changes. Something like a test that first
420 queries GDB for all supported architectures and then feeds each back
421 to GDB.. Anyone interested in learning how to write tests? :-)
425 This list is probably not up to date, and opinions vary about the
426 importance or even desirability of some of the items.
428 Document trace machinery.
430 Document overlay machinery.
432 Extend .gdbinit mechanism to specify name on command line, allow for
433 lists of files to load, include function of --tclcommand.
435 @c This does not work (yet if ever). FIXME.
436 @c @item --parse=@var{lang} @dots{}
437 @c Configure the @value{GDBN} expression parser to parse the listed languages.
438 @c @samp{all} configures @value{GDBN} for all supported languages. To get a
439 @c list of all supported languages, omit the argument. Without this
440 @c option, @value{GDBN} is configured to parse all supported languages.
442 Add an "info bfd" command that displays supported object formats,
443 similarly to objdump -i.
445 START_INFERIOR_TRAPS_EXPECTED need never be defined to 2, since that
446 is its default value. Clean this up.
448 It should be possible to use symbols from shared libraries before we know
449 exactly where the libraries will be loaded. E.g. "b perror" before running
450 the program. This could maybe be done as an extension of the "breakpoint
451 re-evaluation" after new symbols are loaded.
453 Make single_step() insert and remove breakpoints in one operation.
455 Speed up single stepping by avoiding extraneous ptrace calls.
457 Speed up single stepping by not inserting and removing breakpoints
458 each time the inferior starts and stops.
460 Breakpoints should not be inserted and deleted all the time. Only the
461 one(s) there should be removed when we have to step over one. Support
462 breakpoints that don't have to be removed to step over them.
464 Update gdbint.texinfo to include doc on the directory structure and
465 the various tricks of building gdb.
467 Do a tutorial in gdb.texinfo on how to do simple things in gdb.
468 E.g. how to set a breakpoint that just prints something and continues.
469 How to break on aborts. Etc.
471 Provide "voodoo" debugging of core files. This creates a zombie
472 process as a child of the debugger, and loads it up with the data,
473 stack, and regs of the core file. This allows you to call functions
474 in the executable, to manipulate the data in the core file.
476 GDB reopens the source file on every line, as you "next" through it.
478 Referencing the vtbl member of a struct doesn't work. It prints OK
479 if you print the struct, but it gets 0 if you try to deref it.
481 Persistent command history: A feature where you could save off a list
482 of the commands you did, so you can edit it into something that will bring
483 the target to the same place every time you source it.
484 This would also be useful for automated fast watchpointing; if you go
485 past the place where it watchpoints, you just start it over again and
486 do it more carefully.
488 Deal with the SunOS 4.0 and 4.1.1 ptrace bug that loses the registers if
489 the stack is paged out.
491 Finish the C++ exception handling stub routines. Lint points them out
492 as unused statics functions.
494 Perhaps "i source" should take an argument like that of "list".
496 See if core-aout.c's fetch_core_registers can be used on more machines.
497 E.g. MIPS (mips-xdep.c).
499 unpack_double() does not handle IEEE float on the target unless the host
500 is also IEEE. Death on a vax.
502 Set up interface between GDB and INFO so that you can hop into interactive
503 INFO and back out again. When running under Emacs, should use Emacs
504 info, else fork the info program. Installation of GDB should install
505 its texinfo files into the info tree automagically, including the readline
508 "help address" ought to find the "help set print address" entry.
510 Remove the VTBL internal guts from printouts of C++ structs, unless
513 Remove "at 0xnnnn" from the "b foo" response, if `print address off' and if
514 it matches the source line indicated.
516 The prompt at end of screen should accept space as well as CR.
518 Check STORE_RETURN_VALUE on all architectures. Check near it in tm-sparc.h
519 for other bogosities.
521 Check for storage leaks in GDB, I'm sure there are a lot!
523 vtblprint of a vtbl should demangle the names it's printing.
525 Backtrace should point out what the currently selected frame is, in
526 its display, perhaps showing "@3 foo (bar, ...)" or ">3 foo (bar,
527 ...)" rather than "#3 foo (bar, ...)".
529 "i program" should work for core files, and display more info, like what
530 actually caused it to die.
532 "x/10i" should shorten the long name, if any, on subsequent lines.
534 Check through the code for FIXME comments and fix them. dbxread.c,
535 blockframe.c, and plenty more. (I count 634 as of 940621 - sts)
537 "next" over a function that longjumps, never stops until next time you happen
538 to get to that spot by accident. E.g. "n" over execute_command which has
541 "set zeroprint off", don't bother printing members of structs which
542 are entirely zero. Useful for those big structs with few useful
545 GDB does four ioctl's for every command, probably switching terminal modes
546 to/from inferior or for readline or something.
548 terminal_ours versus terminal_inferior: cache state. Switch should be a noop
549 if the state is the same, too.
553 Clean up invalid_float handling so gdb doesn't coredump when it tries to
554 access a NaN. While this might work on SPARC, other machines are not
557 "b value_at ; commands ; continue ; end" stops EVERY OTHER TIME!
558 Then once you enter a command, it does the command, runs two more
559 times, and then stops again! Bizarre... (This behaviour has been
560 modified, but it is not yet 100% predictable when e.g. the commands
561 call functions in the child, and while there, the child is interrupted
562 with a signal, or hits a breakpoint.)
564 help completion, help history should work.
566 Check that we can handle stack trace through varargs AND alloca in same
569 wait_for_inferior loops forever if wait() gives it an error.
571 "i frame" shows wrong "arglist at" location, doesn't show where the args
572 should be found, only their actual values.
574 There should be a way for "set" commands to validate the new setting
575 before it takes effect.
577 A mess of floating point opcodes are missing from sparc-opcode.h.
578 Also, a little program should test the table for bits that are
579 overspecified or underspecified. E.g. if the must-be-ones bits
580 and the must-be-zeroes bits leave some fields unexamined, and the format
581 string leaves them unprinted, then point this out. If multiple
582 non-alias patterns match, point this out too. Finally, there should
583 be a sparc-optest.s file that tries each pattern out. This file
584 should end up coming back the same (modulo transformation comments)
585 if fed to "gas" then the .o is fed to gdb for disassembly.
587 Eliminate all the core_file_command's in all the xdep files.
588 Eliminate separate declarations of registers[] everywhere.
590 "ena d" is ambiguous, why? "ena delete" seems to think it is a command!
592 Perhaps move the tdep, xdep, and nat files, into the config
593 subdirectories. If not, at least straighten out their names so that
594 they all start with the machine name.
596 inferior_status should include stop_print_frame. It won't need to be
597 reset in wait_for_inferior after bpstat_stop_status call, then.
599 i line VAR produces "Line number not known for symbol ``var''.". I
600 thought we were stashing that info now!
602 We should be able to write to random files at hex offsets like adb.
604 Make "target xxx" command interruptible.
606 Handle add_file with separate text, data, and bss addresses. Maybe
607 handle separate addresses for each segment in the object file?
609 Handle free_named_symtab to cope with multiply-loaded object files
610 in a dynamic linking environment. Should remember the last copy loaded,
611 but not get too snowed if it finds references to the older copy.
613 Generalize and Standardize the RPC interface to a target program,
614 improve it beyond the "ptrace" interface, and see if it can become a
615 standard for remote debugging. (This is talking about the vxworks
616 interface. Seems unlikely to me that there will be "a standard" for
617 remote debugging anytime soon --kingdon, 8 Nov 1994).
619 Remove all references to:
626 now that we have BFD. All remaining are in machine dependent files.
628 When quitting with a running program, if a core file was previously
629 examined, you get "Couldn't read float regs from core file"...if
630 indeed it can't. generic_mourn_inferior...
632 Have remote targets give a warning on a signal argument to
633 target_resume. Or better yet, extend the protocols so that it works
634 like it does on the Unix-like systems.
636 Sort help and info output.
638 Re-organize help categories into things that tend to fit on a screen
641 renote-nindy.c handles interrupts poorly; it error()s out of badly
642 chosen places, e.g. leaving current_frame zero, which causes core dumps
645 Add in commands like ADB's for searching for patterns, etc. We should
646 be able to examine and patch raw unsymboled binaries as well in gdb as
647 we can in adb. (E.g. increase the timeout in /bin/login without source).
649 Those xdep files that call register_addr without defining it are
650 probably simply broken. When reconfiguring this part of gdb, I could
651 only make guesses about how to redo some of those files, and I
652 probably guessed wrong, or left them "for later" when I have a
653 machine that can attempt to build them.
655 When doing "step" or "next", if a few lines of source are skipped between
656 the previous line and the current one, print those lines, not just the
657 last line of a multiline statement.
659 When searching for C++ superclasses in value_cast in valops.c, we must
660 not search the "fields", only the "superclasses". There might be a
661 struct with a field name that matches the superclass name. This can
662 happen when the struct was defined before the superclass (before the
663 name became a typedef).
665 Handling of "&" address-of operator needs some serious overhaul
666 for ANSI C and consistency on arrays and functions.
667 For "float point[15];":
668 ptype &point[4] ==> Attempt to take address of non-lvalue.
669 For "char *malloc();":
670 ptype malloc ==> "char *()"; should be same as
671 ptype &malloc ==> "char *(*)()"
672 call printf ("%x\n", malloc) ==> weird value, should be same as
673 call printf ("%x\n", &malloc) ==> correct value
675 Fix dbxread.c symbol reading in the presence of interrupts. It
676 currently leaves a cleanup to blow away the entire symbol table when a
677 QUIT occurs. (What's wrong with that? -kingdon, 28 Oct 1993).
679 Mipsread.c reads include files depth-first, because the dependencies
680 in the psymtabs are way too inclusive (it seems to me). Figure out what
681 really depends on what, to avoid recursing 20 or 30 times while reading
684 value_add() should be subtracting the lower bound of arrays, if known,
685 and possibly checking against the upper bound for error reporting.
687 mipsread.c symbol table allocation and deallocation should be checked.
688 My suspicion is that it's full of memory leaks.
690 SunOS should have a target_lookup_symbol() for common'd things allocated
691 by the shared library linker ld.so.
693 When listing source lines, check for a preceding \n, to verify that
694 the file hasn't changed out from under us.
696 When listing source lines, eat leading whitespace corresponding to the
697 line-number prefix we print. This avoids long lines wrapping.
699 mipsread.c needs to check for old symtabs and psymtabs for the same
700 files, the way it happens for dbxread.c and coffread.c, for VxWorks
701 incremental symbol table reloading.
703 Get all the remote systems (where the protocol allows it) to be able to
704 stop the remote system when the GDB user types ^C (like remote.c
705 does). For ebmon, use ^Ak.
707 Possible feature: A version of the "disassemble" command which shows
708 both source and assembly code ("set symbol-filename on" is a partial
711 investigate "x/s 0" (right now stops early) (I think maybe GDB is
712 using a 0 address for bad purposes internally).
714 Make "info path" and path_command work again (but independent of the
715 environment either of gdb or that we'll pass to the inferior).
717 Make GDB understand the GCC feature for putting octal constants in
718 enums. Make it so overflow on an enum constant does not error_type
719 the whole type. Allow arbitrarily large enums with type attributes.
720 Put all this stuff in the testsuite.
722 Make TYPE_CODE_ERROR with a non-zero TYPE_LENGTH more useful (print
723 the value in hex; process type attributes). Add this to the
724 testsuite. This way future compilers can add new types and old
725 versions of GDB can do something halfway reasonable.
727 Clean up formatting of "info registers" on MIPS and 88k. See if it
728 is possible to do this generically across all target architectures.
730 GDB gets bfd/corefile.c and gdb/corefile.c confused (this should be easy to
731 repeat even with something more recent than GDB 4.9).
733 Check that unmatched RBRAC doesn't abort().
735 Fix mdebugread.c:parse_type to do fundamental types right (see
736 rs6000_builtin_type in stabsread.c for what "right" is--the point is
737 that the debug format fixes the sizes of these things and it shouldn't
738 depend on stuff like TARGET_PTR_BIT and so on. For mdebug, there seem
739 to be separate bt* codes for 64 bit and 32 bit things, and GDB should
740 be aware of that). Also use a switch statement for clarity and speed.
742 Investigate adding symbols in target_load--some targets do, some
745 Put dirname in psymtabs and change lookup*symtab to use dirname (so
746 /foo/bar.c works whether compiled by cc /foo/bar.c, or cd /foo; cc
749 Merge xcoffread.c and coffread.c. Use breakpoint_re_set instead of
752 Fix byte order and int size sins in tm-a29k.h
753 (EXTRACT_RETURN_VALUE). Perhaps should reproduce bug and verify fix
754 (or perhaps should just fix it...).
756 Make a watchpoint on a constant expression an error (or warning
759 Make a watchpoint which contains a function call an error (it is
760 broken now, making it work is probably not worth the effort).
762 Re-do calls to signal() in remote.c, and inflow.c (set_sigint_trap and
763 so on) to be independent of the debugging target, using target_stop to
764 stop the inferior. Probably the part which is now handled by
765 interrupt_query in remote.c can be done without any new features in
766 the debugging target.
768 New test case based on weird.exp but in which type numbers are not
769 renumbered (thus multiply defining a type). This currently causes an
770 infinite loop on "p v_comb".
776 "source file more recent" loses on re-read
778 Fix 386 floating point so that floating point registers are real
779 registers (but code can deal at run-time if they are missing, like
780 mips and 68k). This would clean up "info float" and related stuff.
782 Look at Solaris bug in interrupt.exp. Can get out of syscall with
783 PRSABORT (syscall will return EINTR) but merely doing that leads to a
784 "can't read memory" error.
786 gcc -g -c enummask.c then gdb enummask.o, then "p v". GDB complains
787 about not being able to access memory location 0.
789 -------------------- enummask.c
808 If try to modify value in file with "set write off" should give
809 appropriate error not "cannot access memory at address 0x65e0".
811 Why do we allow a target to omit standard register names (NO_STD_REGS
812 in tm-z8k.h)? I thought the standard register names were supposed to
813 be just that, standard.
815 Allow core file without exec file on RS/6000.
817 Make sure "shell" with no arguments works right on DOS.
819 Make gdb.ini (as well as .gdbinit) be checked on all platforms, so
820 the same directory can be NFS-mounted on unix or DOS, and work the
823 cd ~/tmp/<M-?> causes infinite loop (where ~/tmp is a directory).
825 Get SECT_OFF_TEXT stuff out of objfile_relocate (might be needed to
826 get RS/6000 to work right, might not be immediately relevant).
828 Clean up add_toc_to_loadinfo
830 Think about attached processes and sharing terminal.
832 John sez in reference to ignoring errors from tcsegpgrp if attach_flag:
833 set_tty_state should not have any trouble with attached processes.
834 Instead, the tty handling should leave the pgrp of the tty alone when
835 attaching to processes (perhaps pass terminal_init_inferior a flag
836 saying whether we're attaching).
838 PAGE_SIZE redefined warnings on AIX. Probably should be using
839 BFD_PAGE_SIZE throughout BFD.
841 Rewrite proceed, wait_for_inferior, and normal_stop to clean them up.
844 1) Make each test in wait_for_inferior a seperate subroutine
846 2) Combine wait_for_inferior and normal_stop to clean up
847 communication via global variables.
848 3) See if you can find some way to clean up the global
849 variables that are used; possibly group them by data flow
850 and information content?
852 Work out some kind of way to allow running the inferior to be done as
853 a sub-execution of, eg. breakpoint command lists. Currently running
854 the inferior interupts any command list execution. This would require
855 some rewriting of wait_for_inferior & friends, and hence should
856 probably be done in concert with the above.
858 Add function arguments to gdb user defined functions.
860 Add convenience variables that refer to exec file, symbol file,
861 selected frame source file, selected frame function, selected frame
864 Add a "suspend" subcommand of the "continue" command to suspend gdb
865 while continuing execution of the subprocess. Useful when you are
866 debugging servers and you want to dodge out and initiate a connection
867 to a server running under gdb.
869 Add stab information to allow reasonable debugging of inline functions
870 (possibly they should show up on a stack backtrace? With a note
871 indicating that they weren't "real"?).
873 Modify the naked "until" command to step until past the current source
874 line, rather than past the current pc value. This is tricky simply
875 because the low level routines have no way of specifying a multi-line
876 step range, and there is no way of saying "don't print stuff when we
877 stop" from above (otherwise could just call step many times).
879 Modify the handling of symbols grouped through BINCL/EINCL stabs to
880 allocate a partial symtab for each BINCL/EINCL grouping. This will
881 seriously decrease the size of inter-psymtab dependencies and hence
882 lessen the amount that needs to be read in when a new source file is
885 Do an "x/i $pc" after each stepi or nexti.
887 Modify all of the disassemblers to use printf_filtered to get correct
890 Modify gdb to work correctly with Pascal.
892 Add a command for searching memory, a la adb. It specifies size,
893 mask, value, start address. ADB searches until it finds it or hits
894 an error (or is interrupted).
896 Remove the range and type checking code and documentation, if not