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.
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 gdb-cvs fails to build on freebsd-elf
32 http://sourceware.cygnus.com/ml/gdb/2000-04/msg00004.html
34 Either the FreeBSD group need to contribute their local GDB changes
35 back to the master sources or someone needs to provides a new
36 (clean-room) implementation. Since the former involves a fairly
37 complicated assignment the latter may be easier. [cagney]
41 Generic: lin-thread cannot handle thread exit (Mark Kettenis, Michael
42 Snyder) http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00525.html
44 The thread_db assisted debugging code doesn't handle exiting threads
45 properly, at least in combination with glibc 2.1.3 (the framework is
46 there, just not the actual code). There are at least two problems
47 that prevent this from working.
49 As an additional reference point, the pre thread_db code did not work
54 Java (Anthony Green, David Taylor)
56 Anthony Green has a number of Java patches that did not make it into
60 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00512.html
63 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00515.html
65 Patch: handle N_MAIN stab
66 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00527.html
70 Pascal (Pierre Muller, David Taylor)
72 Pierre Muller has contributed patches for adding Pascal Language
75 2 pascal language patches inserted in database
76 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00521.html
79 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00496.html
83 GNU/Linux/x86 and random thread signals (and Solaris/SPARC but not
85 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00336.html
87 Christopher Blizzard writes:
89 So, I've done some more digging into this and it looks like Jim
90 Kingdon has reported this problem in the past:
92 http://sourceware.cygnus.com/ml/bug-gdb/1999-10/msg00058.html
94 I can reproduce this problem both with and without Tom's patch. Has
95 anyone seen this before? Maybe have a solution for it hanging around?
98 There's a test case for this documented at:
100 when debugging threaded applications you get extra SIGTRAPs
101 http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=9565
103 [There should be a GDB testcase - cagney]
107 Possible regressions with some devel GCCs.
108 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00475.html
110 gcc-2.95.2 outputs a line note *before* the prologue (and one for the
111 closing brace after the epilogue, instead of before it, as it used to
112 be). By disabling the RTL-style prologue generating mechanism
113 (undocumented GCC option -mno-schedule-prologue), you get back the
114 traditional behaviour.
115 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00510.html
117 This should now be fixed.
121 RFD: infrun.c: No bpstat_stop_status call after proceed over break?
123 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00665.html
125 GDB misses watchpoint triggers after proceeding over a breakpoint on
129 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00664.html
134 x86 linux GDB and SIGALRM (???)
135 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00803.html
137 I know there are problems with single stepping through signal
138 handlers. These problems were present in 4.18. They were just masked
139 because 4.18 failed to recognize signal handlers. Fixing it is not
140 easy, and will require changes to handle_inferior_event(), that I
141 prefer not to make before the 5.0 release.
147 MI documentation in GDB user guide. (Andrew Cagney, Elena Zannoni,
148 Stan Shebs, anyone else?)
150 > (Are there plans to make gdbmi.texi be part of the manual as well?)
152 I'd like to see it go in there sooner rather than later too. Otherwise
153 you're introducing discrepancies between the manual and the documentation,
154 and everybody is confused - witness the lack of doc for the tracing
155 commands still, some two years after they were added...
157 Discussion on MI can be found on the thread: [PATCH] GDB command-line
158 switches and annotations docs
159 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00639.html
161 MI documentation can be found in the file gdb/mi/gdbmi.texinfo
165 Revised UDP support (was: Re: [Fwd: [patch] UDP transport support])
166 http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00000.html
168 (Broken) support for GDB's remote protocol across UDP is to be
169 included in the follow-on release.
173 GDB 5.0: Test results
174 =====================
178 o the output of `config.guess`
181 o a note mentioning the reason
182 for any serious failures.
186 alpha-dec-osf4.0a, vendor compiler, 2000-03-04
188 Still has many compile warnings (mostly relating back to PTR vs void*)
189 but it did compile using:
196 # of expected passes 6223
197 # of unexpected failures 103
198 # of unexpected successes 2
199 # of expected failures 196
200 # of unresolved testcases 6
201 # of unsupported tests 1
203 Looking at the output it would appear that GDB is stepping into some
204 functions instead of ``next'' ing over them:
208 dummy () at /home/cagney/GDB-DEJAGNU/src/gdb/testsuite/gdb.base/all-types.c:41
211 Since there is no active maintainer, I'd consider this sufficient for
216 sparc-sun-solaris2.6, egcs-2.91.66, 2000-02-10
217 http://sourceware.cygnus.com/ml/gdb-testers/2000-q1/msg00030.html
219 There is a SIGTRAP problem that occures in ptrace.exp (Cagney to
222 # of expected passes 6420
223 # of unexpected failures 7
224 # of expected failures 199
228 solaris 2.5.1 sparc?, 2.9-gnupro-99r1, 2000-02-10
229 http://sourceware.cygnus.com/ml/gdb-testers/2000-q1/msg00032.html
231 # of expected passes 6420
232 # of unexpected failures 6
233 # of expected failures 199
237 sparc-unknown-netbsdelf1.4P, egcs-1.1.2+, 2000-03-01
239 This is with a very recent kernel.
241 # of expected passes 6055
242 # of unexpected failures 88
243 # of unexpected successes 1
244 # of expected failures 190
245 # of unresolved testcases 59
250 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00185.html
252 Kevins merged it all in.
258 Builds ok. Problems with some of the thread code. Unfortunate but
259 not a show stopper. Nick D's still looking at it.
261 Re: uw-threads issues
262 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00025.html
265 ------------------------------------------------
271 The following code cleanups are planned for the follow-on release to
278 The need for this as almost been eliminated. The next version of GCC
279 (assuming cagney gets the relevant patch committed) will be able to
280 supress unused parameter warnings.
284 Delete macro TARGET_BYTE_ORDER_SELECTABLE.
286 Patches in the database.
292 Readline 4.? is out. A merge wouldn't hurt.
298 Eliminate all uses of PARAMS in GDB's source code.
302 Elimination of make_cleanup_func. (Andrew Cagney)
304 make_cleanup_func elimination
305 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00791.html
306 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00814.html
310 ChangeLog.mi vs ChangeLog-mi (Andrew Cagney)
311 Needs further debate.
313 Re: [PATCH] Add change-log variables to more MI files
314 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00811.html
318 Re: Various C++ things
320 value_headof/value_from_vtable_info are worthless, and should be removed.
321 The one place in printcmd.c that uses it should use the RTTI functions.
323 RTTI for g++ should be using the typeinfo functions rather than the vtables.
324 The typeinfo functions are always at offset 4 from the beginning of the vtable,
325 and are always right. The vtables will have weird names like E::VB sometimes.
326 The typeinfo function will always be "E type_info function", or somesuch.
328 value_virtual_fn_field needs to be fixed so there are no failures for virtual
329 functions for C++ using g++.
331 Testsuite cases are the major priority right now for C++ support, since i have
332 to make a lot of changes that could potentially break each other.
336 GDBARCH cleanup (Andrew Cagney)
338 The non-generated parts of gdbarch.{sh,h,c} should be separated out
339 into arch-utils.[hc].
341 The ``info architecture'' command should be replaced with a fixed
342 ``set architecture'' (implemented using the command.c enum code).
344 Document that gdbarch_init_ftype could easily fail because it didn't
345 identify an architecture.
349 Migrate qfThreadInfo packet -> qThreadInfo. (Andrew Cagney)
351 Add support for packet enable/disable commands with these thread
352 packets. General cleanup.
354 [PATCH] Document the ThreadInfo remote protocol queries
355 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00832.html
357 [PATCH] "info threads" queries for remote.c
358 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00831.html
362 Eliminate gdb/tui/Makefile.in.
363 Cleanup configury support for optional sub-directories.
365 Check how GCC handles multiple front ends for an example of how things
366 could work. A tentative first step is to rationalize things so that
367 all sub directories are handled in a fashion similar to gdb/mi.
376 Check that GDB can handle all BFD architectures (Andrew Cagney)
378 There should be a test that checks that BFD/GDB are in sync with
379 regard to architecture changes. Something like a test that first
380 queries GDB for all supported architectures and then feeds each back
381 to GDB.. Anyone interested in learning how to write tests? :-)
385 This list is probably not up to date, and opinions vary about the
386 importance or even desirability of some of the items.
388 Document trace machinery.
390 Document overlay machinery.
392 Extend .gdbinit mechanism to specify name on command line, allow for
393 lists of files to load, include function of --tclcommand.
395 @c This does not work (yet if ever). FIXME.
396 @c @item --parse=@var{lang} @dots{}
397 @c Configure the @value{GDBN} expression parser to parse the listed languages.
398 @c @samp{all} configures @value{GDBN} for all supported languages. To get a
399 @c list of all supported languages, omit the argument. Without this
400 @c option, @value{GDBN} is configured to parse all supported languages.
402 Add an "info bfd" command that displays supported object formats,
403 similarly to objdump -i.
405 START_INFERIOR_TRAPS_EXPECTED need never be defined to 2, since that
406 is its default value. Clean this up.
408 It should be possible to use symbols from shared libraries before we know
409 exactly where the libraries will be loaded. E.g. "b perror" before running
410 the program. This could maybe be done as an extension of the "breakpoint
411 re-evaluation" after new symbols are loaded.
413 Make single_step() insert and remove breakpoints in one operation.
415 Speed up single stepping by avoiding extraneous ptrace calls.
417 Speed up single stepping by not inserting and removing breakpoints
418 each time the inferior starts and stops.
420 Breakpoints should not be inserted and deleted all the time. Only the
421 one(s) there should be removed when we have to step over one. Support
422 breakpoints that don't have to be removed to step over them.
424 Update gdbint.texinfo to include doc on the directory structure and
425 the various tricks of building gdb.
427 Do a tutorial in gdb.texinfo on how to do simple things in gdb.
428 E.g. how to set a breakpoint that just prints something and continues.
429 How to break on aborts. Etc.
431 Provide "voodoo" debugging of core files. This creates a zombie
432 process as a child of the debugger, and loads it up with the data,
433 stack, and regs of the core file. This allows you to call functions
434 in the executable, to manipulate the data in the core file.
436 GDB reopens the source file on every line, as you "next" through it.
438 Referencing the vtbl member of a struct doesn't work. It prints OK
439 if you print the struct, but it gets 0 if you try to deref it.
441 Persistent command history: A feature where you could save off a list
442 of the commands you did, so you can edit it into something that will bring
443 the target to the same place every time you source it.
444 This would also be useful for automated fast watchpointing; if you go
445 past the place where it watchpoints, you just start it over again and
446 do it more carefully.
448 Deal with the SunOS 4.0 and 4.1.1 ptrace bug that loses the registers if
449 the stack is paged out.
451 Finish the C++ exception handling stub routines. Lint points them out
452 as unused statics functions.
454 Perhaps "i source" should take an argument like that of "list".
456 See if core-aout.c's fetch_core_registers can be used on more machines.
457 E.g. MIPS (mips-xdep.c).
459 unpack_double() does not handle IEEE float on the target unless the host
460 is also IEEE. Death on a vax.
462 Set up interface between GDB and INFO so that you can hop into interactive
463 INFO and back out again. When running under Emacs, should use Emacs
464 info, else fork the info program. Installation of GDB should install
465 its texinfo files into the info tree automagically, including the readline
468 "help address" ought to find the "help set print address" entry.
470 Remove the VTBL internal guts from printouts of C++ structs, unless
473 Remove "at 0xnnnn" from the "b foo" response, if `print address off' and if
474 it matches the source line indicated.
476 The prompt at end of screen should accept space as well as CR.
478 Check STORE_RETURN_VALUE on all architectures. Check near it in tm-sparc.h
479 for other bogosities.
481 Check for storage leaks in GDB, I'm sure there are a lot!
483 vtblprint of a vtbl should demangle the names it's printing.
485 Backtrace should point out what the currently selected frame is, in
486 its display, perhaps showing "@3 foo (bar, ...)" or ">3 foo (bar,
487 ...)" rather than "#3 foo (bar, ...)".
489 "i program" should work for core files, and display more info, like what
490 actually caused it to die.
492 "x/10i" should shorten the long name, if any, on subsequent lines.
494 Check through the code for FIXME comments and fix them. dbxread.c,
495 blockframe.c, and plenty more. (I count 634 as of 940621 - sts)
497 "next" over a function that longjumps, never stops until next time you happen
498 to get to that spot by accident. E.g. "n" over execute_command which has
501 "set zeroprint off", don't bother printing members of structs which
502 are entirely zero. Useful for those big structs with few useful
505 GDB does four ioctl's for every command, probably switching terminal modes
506 to/from inferior or for readline or something.
508 terminal_ours versus terminal_inferior: cache state. Switch should be a noop
509 if the state is the same, too.
513 Clean up invalid_float handling so gdb doesn't coredump when it tries to
514 access a NaN. While this might work on SPARC, other machines are not
517 "b value_at ; commands ; continue ; end" stops EVERY OTHER TIME!
518 Then once you enter a command, it does the command, runs two more
519 times, and then stops again! Bizarre... (This behaviour has been
520 modified, but it is not yet 100% predictable when e.g. the commands
521 call functions in the child, and while there, the child is interrupted
522 with a signal, or hits a breakpoint.)
524 help completion, help history should work.
526 Check that we can handle stack trace through varargs AND alloca in same
529 wait_for_inferior loops forever if wait() gives it an error.
531 "i frame" shows wrong "arglist at" location, doesn't show where the args
532 should be found, only their actual values.
534 There should be a way for "set" commands to validate the new setting
535 before it takes effect.
537 A mess of floating point opcodes are missing from sparc-opcode.h.
538 Also, a little program should test the table for bits that are
539 overspecified or underspecified. E.g. if the must-be-ones bits
540 and the must-be-zeroes bits leave some fields unexamined, and the format
541 string leaves them unprinted, then point this out. If multiple
542 non-alias patterns match, point this out too. Finally, there should
543 be a sparc-optest.s file that tries each pattern out. This file
544 should end up coming back the same (modulo transformation comments)
545 if fed to "gas" then the .o is fed to gdb for disassembly.
547 Eliminate all the core_file_command's in all the xdep files.
548 Eliminate separate declarations of registers[] everywhere.
550 "ena d" is ambiguous, why? "ena delete" seems to think it is a command!
552 Perhaps move the tdep, xdep, and nat files, into the config
553 subdirectories. If not, at least straighten out their names so that
554 they all start with the machine name.
556 inferior_status should include stop_print_frame. It won't need to be
557 reset in wait_for_inferior after bpstat_stop_status call, then.
559 i line VAR produces "Line number not known for symbol ``var''.". I
560 thought we were stashing that info now!
562 We should be able to write to random files at hex offsets like adb.
564 Make "target xxx" command interruptible.
566 Handle add_file with separate text, data, and bss addresses. Maybe
567 handle separate addresses for each segment in the object file?
569 Handle free_named_symtab to cope with multiply-loaded object files
570 in a dynamic linking environment. Should remember the last copy loaded,
571 but not get too snowed if it finds references to the older copy.
573 Generalize and Standardize the RPC interface to a target program,
574 improve it beyond the "ptrace" interface, and see if it can become a
575 standard for remote debugging. (This is talking about the vxworks
576 interface. Seems unlikely to me that there will be "a standard" for
577 remote debugging anytime soon --kingdon, 8 Nov 1994).
579 Remove all references to:
586 now that we have BFD. All remaining are in machine dependent files.
588 When quitting with a running program, if a core file was previously
589 examined, you get "Couldn't read float regs from core file"...if
590 indeed it can't. generic_mourn_inferior...
592 Have remote targets give a warning on a signal argument to
593 target_resume. Or better yet, extend the protocols so that it works
594 like it does on the Unix-like systems.
596 Sort help and info output.
598 Re-organize help categories into things that tend to fit on a screen
601 renote-nindy.c handles interrupts poorly; it error()s out of badly
602 chosen places, e.g. leaving current_frame zero, which causes core dumps
605 Add in commands like ADB's for searching for patterns, etc. We should
606 be able to examine and patch raw unsymboled binaries as well in gdb as
607 we can in adb. (E.g. increase the timeout in /bin/login without source).
609 Those xdep files that call register_addr without defining it are
610 probably simply broken. When reconfiguring this part of gdb, I could
611 only make guesses about how to redo some of those files, and I
612 probably guessed wrong, or left them "for later" when I have a
613 machine that can attempt to build them.
615 When doing "step" or "next", if a few lines of source are skipped between
616 the previous line and the current one, print those lines, not just the
617 last line of a multiline statement.
619 When searching for C++ superclasses in value_cast in valops.c, we must
620 not search the "fields", only the "superclasses". There might be a
621 struct with a field name that matches the superclass name. This can
622 happen when the struct was defined before the superclass (before the
623 name became a typedef).
625 Handling of "&" address-of operator needs some serious overhaul
626 for ANSI C and consistency on arrays and functions.
627 For "float point[15];":
628 ptype &point[4] ==> Attempt to take address of non-lvalue.
629 For "char *malloc();":
630 ptype malloc ==> "char *()"; should be same as
631 ptype &malloc ==> "char *(*)()"
632 call printf ("%x\n", malloc) ==> weird value, should be same as
633 call printf ("%x\n", &malloc) ==> correct value
635 Fix dbxread.c symbol reading in the presence of interrupts. It
636 currently leaves a cleanup to blow away the entire symbol table when a
637 QUIT occurs. (What's wrong with that? -kingdon, 28 Oct 1993).
639 Mipsread.c reads include files depth-first, because the dependencies
640 in the psymtabs are way too inclusive (it seems to me). Figure out what
641 really depends on what, to avoid recursing 20 or 30 times while reading
644 value_add() should be subtracting the lower bound of arrays, if known,
645 and possibly checking against the upper bound for error reporting.
647 mipsread.c symbol table allocation and deallocation should be checked.
648 My suspicion is that it's full of memory leaks.
650 SunOS should have a target_lookup_symbol() for common'd things allocated
651 by the shared library linker ld.so.
653 When listing source lines, check for a preceding \n, to verify that
654 the file hasn't changed out from under us.
656 When listing source lines, eat leading whitespace corresponding to the
657 line-number prefix we print. This avoids long lines wrapping.
659 mipsread.c needs to check for old symtabs and psymtabs for the same
660 files, the way it happens for dbxread.c and coffread.c, for VxWorks
661 incremental symbol table reloading.
663 Get all the remote systems (where the protocol allows it) to be able to
664 stop the remote system when the GDB user types ^C (like remote.c
665 does). For ebmon, use ^Ak.
667 Possible feature: A version of the "disassemble" command which shows
668 both source and assembly code ("set symbol-filename on" is a partial
671 investigate "x/s 0" (right now stops early) (I think maybe GDB is
672 using a 0 address for bad purposes internally).
674 Make "info path" and path_command work again (but independent of the
675 environment either of gdb or that we'll pass to the inferior).
677 Make GDB understand the GCC feature for putting octal constants in
678 enums. Make it so overflow on an enum constant does not error_type
679 the whole type. Allow arbitrarily large enums with type attributes.
680 Put all this stuff in the testsuite.
682 Make TYPE_CODE_ERROR with a non-zero TYPE_LENGTH more useful (print
683 the value in hex; process type attributes). Add this to the
684 testsuite. This way future compilers can add new types and old
685 versions of GDB can do something halfway reasonable.
687 Clean up formatting of "info registers" on MIPS and 88k. See if it
688 is possible to do this generically across all target architectures.
690 GDB gets bfd/corefile.c and gdb/corefile.c confused (this should be easy to
691 repeat even with something more recent than GDB 4.9).
693 Check that unmatched RBRAC doesn't abort().
695 Fix mdebugread.c:parse_type to do fundamental types right (see
696 rs6000_builtin_type in stabsread.c for what "right" is--the point is
697 that the debug format fixes the sizes of these things and it shouldn't
698 depend on stuff like TARGET_PTR_BIT and so on. For mdebug, there seem
699 to be separate bt* codes for 64 bit and 32 bit things, and GDB should
700 be aware of that). Also use a switch statement for clarity and speed.
702 Investigate adding symbols in target_load--some targets do, some
705 Put dirname in psymtabs and change lookup*symtab to use dirname (so
706 /foo/bar.c works whether compiled by cc /foo/bar.c, or cd /foo; cc
709 Merge xcoffread.c and coffread.c. Use breakpoint_re_set instead of
712 Fix byte order and int size sins in tm-a29k.h
713 (EXTRACT_RETURN_VALUE). Perhaps should reproduce bug and verify fix
714 (or perhaps should just fix it...).
716 Make a watchpoint on a constant expression an error (or warning
719 Make a watchpoint which contains a function call an error (it is
720 broken now, making it work is probably not worth the effort).
722 Re-do calls to signal() in remote.c, and inflow.c (set_sigint_trap and
723 so on) to be independent of the debugging target, using target_stop to
724 stop the inferior. Probably the part which is now handled by
725 interrupt_query in remote.c can be done without any new features in
726 the debugging target.
728 New test case based on weird.exp but in which type numbers are not
729 renumbered (thus multiply defining a type). This currently causes an
730 infinite loop on "p v_comb".
736 "source file more recent" loses on re-read
738 Fix 386 floating point so that floating point registers are real
739 registers (but code can deal at run-time if they are missing, like
740 mips and 68k). This would clean up "info float" and related stuff.
742 Look at Solaris bug in interrupt.exp. Can get out of syscall with
743 PRSABORT (syscall will return EINTR) but merely doing that leads to a
744 "can't read memory" error.
746 gcc -g -c enummask.c then gdb enummask.o, then "p v". GDB complains
747 about not being able to access memory location 0.
749 -------------------- enummask.c
768 If try to modify value in file with "set write off" should give
769 appropriate error not "cannot access memory at address 0x65e0".
771 Why do we allow a target to omit standard register names (NO_STD_REGS
772 in tm-z8k.h)? I thought the standard register names were supposed to
773 be just that, standard.
775 Allow core file without exec file on RS/6000.
777 Make sure "shell" with no arguments works right on DOS.
779 Make gdb.ini (as well as .gdbinit) be checked on all platforms, so
780 the same directory can be NFS-mounted on unix or DOS, and work the
783 cd ~/tmp/<M-?> causes infinite loop (where ~/tmp is a directory).
785 Get SECT_OFF_TEXT stuff out of objfile_relocate (might be needed to
786 get RS/6000 to work right, might not be immediately relevant).
788 Clean up add_toc_to_loadinfo
790 Think about attached processes and sharing terminal.
792 John sez in reference to ignoring errors from tcsegpgrp if attach_flag:
793 set_tty_state should not have any trouble with attached processes.
794 Instead, the tty handling should leave the pgrp of the tty alone when
795 attaching to processes (perhaps pass terminal_init_inferior a flag
796 saying whether we're attaching).
798 PAGE_SIZE redefined warnings on AIX. Probably should be using
799 BFD_PAGE_SIZE throughout BFD.
801 Rewrite proceed, wait_for_inferior, and normal_stop to clean them up.
804 1) Make each test in wait_for_inferior a seperate subroutine
806 2) Combine wait_for_inferior and normal_stop to clean up
807 communication via global variables.
808 3) See if you can find some way to clean up the global
809 variables that are used; possibly group them by data flow
810 and information content?
812 Work out some kind of way to allow running the inferior to be done as
813 a sub-execution of, eg. breakpoint command lists. Currently running
814 the inferior interupts any command list execution. This would require
815 some rewriting of wait_for_inferior & friends, and hence should
816 probably be done in concert with the above.
818 Add function arguments to gdb user defined functions.
820 Add convenience variables that refer to exec file, symbol file,
821 selected frame source file, selected frame function, selected frame
824 Add a "suspend" subcommand of the "continue" command to suspend gdb
825 while continuing execution of the subprocess. Useful when you are
826 debugging servers and you want to dodge out and initiate a connection
827 to a server running under gdb.
829 Add stab information to allow reasonable debugging of inline functions
830 (possibly they should show up on a stack backtrace? With a note
831 indicating that they weren't "real"?).
833 Modify the naked "until" command to step until past the current source
834 line, rather than past the current pc value. This is tricky simply
835 because the low level routines have no way of specifying a multi-line
836 step range, and there is no way of saying "don't print stuff when we
837 stop" from above (otherwise could just call step many times).
839 Modify the handling of symbols grouped through BINCL/EINCL stabs to
840 allocate a partial symtab for each BINCL/EINCL grouping. This will
841 seriously decrease the size of inter-psymtab dependencies and hence
842 lessen the amount that needs to be read in when a new source file is
845 Do an "x/i $pc" after each stepi or nexti.
847 Modify all of the disassemblers to use printf_filtered to get correct
850 Modify gdb to work correctly with Pascal.
852 Add a command for searching memory, a la adb. It specifies size,
853 mask, value, start address. ADB searches until it finds it or hits
854 an error (or is interrupted).
856 Remove the range and type checking code and documentation, if not