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 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.
196 ------------------------------------------------
201 The following code cleanups are planned for the follow-on release to
208 The need for this as almost been eliminated. The next version of GCC
209 (assuming cagney gets the relevant patch committed) will be able to
210 supress unused parameter warnings.
214 Delete macro TARGET_BYTE_ORDER_SELECTABLE.
216 Patches in the database.
222 Readline 4.? is out. A merge wouldn't hurt.
228 Eliminate all uses of PARAMS in GDB's source code.
232 Elimination of make_cleanup_func. (Andrew Cagney)
234 make_cleanup_func elimination
235 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00791.html
236 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00814.html
240 ChangeLog.mi vs ChangeLog-mi (Andrew Cagney)
241 Needs further debate.
243 Re: [PATCH] Add change-log variables to more MI files
244 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00811.html
248 Re: Various C++ things
250 value_headof/value_from_vtable_info are worthless, and should be removed.
251 The one place in printcmd.c that uses it should use the RTTI functions.
253 RTTI for g++ should be using the typeinfo functions rather than the vtables.
254 The typeinfo functions are always at offset 4 from the beginning of the vtable,
255 and are always right. The vtables will have weird names like E::VB sometimes.
256 The typeinfo function will always be "E type_info function", or somesuch.
258 value_virtual_fn_field needs to be fixed so there are no failures for virtual
259 functions for C++ using g++.
261 Testsuite cases are the major priority right now for C++ support, since i have
262 to make a lot of changes that could potentially break each other.
266 GDBARCH cleanup (Andrew Cagney)
268 The non-generated parts of gdbarch.{sh,h,c} should be separated out
269 into arch-utils.[hc].
271 The ``info architecture'' command should be replaced with a fixed
272 ``set architecture'' (implemented using the command.c enum code).
274 Document that gdbarch_init_ftype could easily fail because it didn't
275 identify an architecture.
279 Migrate qfThreadInfo packet -> qThreadInfo. (Andrew Cagney)
281 Add support for packet enable/disable commands with these thread
282 packets. General cleanup.
284 [PATCH] Document the ThreadInfo remote protocol queries
285 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00832.html
287 [PATCH] "info threads" queries for remote.c
288 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00831.html
292 Eliminate gdb/tui/Makefile.in.
293 Cleanup configury support for optional sub-directories.
295 Check how GCC handles multiple front ends for an example of how things
296 could work. A tentative first step is to rationalize things so that
297 all sub directories are handled in a fashion similar to gdb/mi.
301 [PATCH/5] src/intl/Makefile.in:distclean additions
302 http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00363.html
304 Do not forget to merge the patch back into the trunk.
308 Re: [RFC] Change configure.in so -W arnings match reality
309 http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00350.html
311 Some GCC compilers do not like -Wreturn-type. (Going forward there
312 may be more problems like that). Need to check which of the warning
313 options are valid. Need to probably disable warnings by default.
322 Check that GDB can handle all BFD architectures (Andrew Cagney)
324 There should be a test that checks that BFD/GDB are in sync with
325 regard to architecture changes. Something like a test that first
326 queries GDB for all supported architectures and then feeds each back
327 to GDB.. Anyone interested in learning how to write tests? :-)
331 This list is probably not up to date, and opinions vary about the
332 importance or even desirability of some of the items.
334 Document trace machinery.
336 Document overlay machinery.
338 Extend .gdbinit mechanism to specify name on command line, allow for
339 lists of files to load, include function of --tclcommand.
341 @c This does not work (yet if ever). FIXME.
342 @c @item --parse=@var{lang} @dots{}
343 @c Configure the @value{GDBN} expression parser to parse the listed languages.
344 @c @samp{all} configures @value{GDBN} for all supported languages. To get a
345 @c list of all supported languages, omit the argument. Without this
346 @c option, @value{GDBN} is configured to parse all supported languages.
348 Add an "info bfd" command that displays supported object formats,
349 similarly to objdump -i.
351 START_INFERIOR_TRAPS_EXPECTED need never be defined to 2, since that
352 is its default value. Clean this up.
354 It should be possible to use symbols from shared libraries before we know
355 exactly where the libraries will be loaded. E.g. "b perror" before running
356 the program. This could maybe be done as an extension of the "breakpoint
357 re-evaluation" after new symbols are loaded.
359 Make single_step() insert and remove breakpoints in one operation.
361 Speed up single stepping by avoiding extraneous ptrace calls.
363 Speed up single stepping by not inserting and removing breakpoints
364 each time the inferior starts and stops.
366 Breakpoints should not be inserted and deleted all the time. Only the
367 one(s) there should be removed when we have to step over one. Support
368 breakpoints that don't have to be removed to step over them.
370 Update gdbint.texinfo to include doc on the directory structure and
371 the various tricks of building gdb.
373 Do a tutorial in gdb.texinfo on how to do simple things in gdb.
374 E.g. how to set a breakpoint that just prints something and continues.
375 How to break on aborts. Etc.
377 Provide "voodoo" debugging of core files. This creates a zombie
378 process as a child of the debugger, and loads it up with the data,
379 stack, and regs of the core file. This allows you to call functions
380 in the executable, to manipulate the data in the core file.
382 GDB reopens the source file on every line, as you "next" through it.
384 Referencing the vtbl member of a struct doesn't work. It prints OK
385 if you print the struct, but it gets 0 if you try to deref it.
387 Persistent command history: A feature where you could save off a list
388 of the commands you did, so you can edit it into something that will bring
389 the target to the same place every time you source it.
390 This would also be useful for automated fast watchpointing; if you go
391 past the place where it watchpoints, you just start it over again and
392 do it more carefully.
394 Deal with the SunOS 4.0 and 4.1.1 ptrace bug that loses the registers if
395 the stack is paged out.
397 Finish the C++ exception handling stub routines. Lint points them out
398 as unused statics functions.
400 Perhaps "i source" should take an argument like that of "list".
402 See if core-aout.c's fetch_core_registers can be used on more machines.
403 E.g. MIPS (mips-xdep.c).
405 unpack_double() does not handle IEEE float on the target unless the host
406 is also IEEE. Death on a vax.
408 Set up interface between GDB and INFO so that you can hop into interactive
409 INFO and back out again. When running under Emacs, should use Emacs
410 info, else fork the info program. Installation of GDB should install
411 its texinfo files into the info tree automagically, including the readline
414 "help address" ought to find the "help set print address" entry.
416 Remove the VTBL internal guts from printouts of C++ structs, unless
419 Remove "at 0xnnnn" from the "b foo" response, if `print address off' and if
420 it matches the source line indicated.
422 The prompt at end of screen should accept space as well as CR.
424 Check STORE_RETURN_VALUE on all architectures. Check near it in tm-sparc.h
425 for other bogosities.
427 Check for storage leaks in GDB, I'm sure there are a lot!
429 vtblprint of a vtbl should demangle the names it's printing.
431 Backtrace should point out what the currently selected frame is, in
432 its display, perhaps showing "@3 foo (bar, ...)" or ">3 foo (bar,
433 ...)" rather than "#3 foo (bar, ...)".
435 "i program" should work for core files, and display more info, like what
436 actually caused it to die.
438 "x/10i" should shorten the long name, if any, on subsequent lines.
440 Check through the code for FIXME comments and fix them. dbxread.c,
441 blockframe.c, and plenty more. (I count 634 as of 940621 - sts)
443 "next" over a function that longjumps, never stops until next time you happen
444 to get to that spot by accident. E.g. "n" over execute_command which has
447 "set zeroprint off", don't bother printing members of structs which
448 are entirely zero. Useful for those big structs with few useful
451 GDB does four ioctl's for every command, probably switching terminal modes
452 to/from inferior or for readline or something.
454 terminal_ours versus terminal_inferior: cache state. Switch should be a noop
455 if the state is the same, too.
459 Clean up invalid_float handling so gdb doesn't coredump when it tries to
460 access a NaN. While this might work on SPARC, other machines are not
463 "b value_at ; commands ; continue ; end" stops EVERY OTHER TIME!
464 Then once you enter a command, it does the command, runs two more
465 times, and then stops again! Bizarre... (This behaviour has been
466 modified, but it is not yet 100% predictable when e.g. the commands
467 call functions in the child, and while there, the child is interrupted
468 with a signal, or hits a breakpoint.)
470 help completion, help history should work.
472 Check that we can handle stack trace through varargs AND alloca in same
475 wait_for_inferior loops forever if wait() gives it an error.
477 "i frame" shows wrong "arglist at" location, doesn't show where the args
478 should be found, only their actual values.
480 There should be a way for "set" commands to validate the new setting
481 before it takes effect.
483 A mess of floating point opcodes are missing from sparc-opcode.h.
484 Also, a little program should test the table for bits that are
485 overspecified or underspecified. E.g. if the must-be-ones bits
486 and the must-be-zeroes bits leave some fields unexamined, and the format
487 string leaves them unprinted, then point this out. If multiple
488 non-alias patterns match, point this out too. Finally, there should
489 be a sparc-optest.s file that tries each pattern out. This file
490 should end up coming back the same (modulo transformation comments)
491 if fed to "gas" then the .o is fed to gdb for disassembly.
493 Eliminate all the core_file_command's in all the xdep files.
494 Eliminate separate declarations of registers[] everywhere.
496 "ena d" is ambiguous, why? "ena delete" seems to think it is a command!
498 Perhaps move the tdep, xdep, and nat files, into the config
499 subdirectories. If not, at least straighten out their names so that
500 they all start with the machine name.
502 inferior_status should include stop_print_frame. It won't need to be
503 reset in wait_for_inferior after bpstat_stop_status call, then.
505 i line VAR produces "Line number not known for symbol ``var''.". I
506 thought we were stashing that info now!
508 We should be able to write to random files at hex offsets like adb.
510 Make "target xxx" command interruptible.
512 Handle add_file with separate text, data, and bss addresses. Maybe
513 handle separate addresses for each segment in the object file?
515 Handle free_named_symtab to cope with multiply-loaded object files
516 in a dynamic linking environment. Should remember the last copy loaded,
517 but not get too snowed if it finds references to the older copy.
519 Generalize and Standardize the RPC interface to a target program,
520 improve it beyond the "ptrace" interface, and see if it can become a
521 standard for remote debugging. (This is talking about the vxworks
522 interface. Seems unlikely to me that there will be "a standard" for
523 remote debugging anytime soon --kingdon, 8 Nov 1994).
525 Remove all references to:
532 now that we have BFD. All remaining are in machine dependent files.
534 When quitting with a running program, if a core file was previously
535 examined, you get "Couldn't read float regs from core file"...if
536 indeed it can't. generic_mourn_inferior...
538 Have remote targets give a warning on a signal argument to
539 target_resume. Or better yet, extend the protocols so that it works
540 like it does on the Unix-like systems.
542 Sort help and info output.
544 Re-organize help categories into things that tend to fit on a screen
547 renote-nindy.c handles interrupts poorly; it error()s out of badly
548 chosen places, e.g. leaving current_frame zero, which causes core dumps
551 Add in commands like ADB's for searching for patterns, etc. We should
552 be able to examine and patch raw unsymboled binaries as well in gdb as
553 we can in adb. (E.g. increase the timeout in /bin/login without source).
555 Those xdep files that call register_addr without defining it are
556 probably simply broken. When reconfiguring this part of gdb, I could
557 only make guesses about how to redo some of those files, and I
558 probably guessed wrong, or left them "for later" when I have a
559 machine that can attempt to build them.
561 When doing "step" or "next", if a few lines of source are skipped between
562 the previous line and the current one, print those lines, not just the
563 last line of a multiline statement.
565 When searching for C++ superclasses in value_cast in valops.c, we must
566 not search the "fields", only the "superclasses". There might be a
567 struct with a field name that matches the superclass name. This can
568 happen when the struct was defined before the superclass (before the
569 name became a typedef).
571 Handling of "&" address-of operator needs some serious overhaul
572 for ANSI C and consistency on arrays and functions.
573 For "float point[15];":
574 ptype &point[4] ==> Attempt to take address of non-lvalue.
575 For "char *malloc();":
576 ptype malloc ==> "char *()"; should be same as
577 ptype &malloc ==> "char *(*)()"
578 call printf ("%x\n", malloc) ==> weird value, should be same as
579 call printf ("%x\n", &malloc) ==> correct value
581 Fix dbxread.c symbol reading in the presence of interrupts. It
582 currently leaves a cleanup to blow away the entire symbol table when a
583 QUIT occurs. (What's wrong with that? -kingdon, 28 Oct 1993).
585 Mipsread.c reads include files depth-first, because the dependencies
586 in the psymtabs are way too inclusive (it seems to me). Figure out what
587 really depends on what, to avoid recursing 20 or 30 times while reading
590 value_add() should be subtracting the lower bound of arrays, if known,
591 and possibly checking against the upper bound for error reporting.
593 mipsread.c symbol table allocation and deallocation should be checked.
594 My suspicion is that it's full of memory leaks.
596 SunOS should have a target_lookup_symbol() for common'd things allocated
597 by the shared library linker ld.so.
599 When listing source lines, check for a preceding \n, to verify that
600 the file hasn't changed out from under us.
602 When listing source lines, eat leading whitespace corresponding to the
603 line-number prefix we print. This avoids long lines wrapping.
605 mipsread.c needs to check for old symtabs and psymtabs for the same
606 files, the way it happens for dbxread.c and coffread.c, for VxWorks
607 incremental symbol table reloading.
609 Get all the remote systems (where the protocol allows it) to be able to
610 stop the remote system when the GDB user types ^C (like remote.c
611 does). For ebmon, use ^Ak.
613 Possible feature: A version of the "disassemble" command which shows
614 both source and assembly code ("set symbol-filename on" is a partial
617 investigate "x/s 0" (right now stops early) (I think maybe GDB is
618 using a 0 address for bad purposes internally).
620 Make "info path" and path_command work again (but independent of the
621 environment either of gdb or that we'll pass to the inferior).
623 Make GDB understand the GCC feature for putting octal constants in
624 enums. Make it so overflow on an enum constant does not error_type
625 the whole type. Allow arbitrarily large enums with type attributes.
626 Put all this stuff in the testsuite.
628 Make TYPE_CODE_ERROR with a non-zero TYPE_LENGTH more useful (print
629 the value in hex; process type attributes). Add this to the
630 testsuite. This way future compilers can add new types and old
631 versions of GDB can do something halfway reasonable.
633 Clean up formatting of "info registers" on MIPS and 88k. See if it
634 is possible to do this generically across all target architectures.
636 GDB gets bfd/corefile.c and gdb/corefile.c confused (this should be easy to
637 repeat even with something more recent than GDB 4.9).
639 Check that unmatched RBRAC doesn't abort().
641 Fix mdebugread.c:parse_type to do fundamental types right (see
642 rs6000_builtin_type in stabsread.c for what "right" is--the point is
643 that the debug format fixes the sizes of these things and it shouldn't
644 depend on stuff like TARGET_PTR_BIT and so on. For mdebug, there seem
645 to be separate bt* codes for 64 bit and 32 bit things, and GDB should
646 be aware of that). Also use a switch statement for clarity and speed.
648 Investigate adding symbols in target_load--some targets do, some
651 Put dirname in psymtabs and change lookup*symtab to use dirname (so
652 /foo/bar.c works whether compiled by cc /foo/bar.c, or cd /foo; cc
655 Merge xcoffread.c and coffread.c. Use breakpoint_re_set instead of
658 Fix byte order and int size sins in tm-a29k.h
659 (EXTRACT_RETURN_VALUE). Perhaps should reproduce bug and verify fix
660 (or perhaps should just fix it...).
662 Make a watchpoint on a constant expression an error (or warning
665 Make a watchpoint which contains a function call an error (it is
666 broken now, making it work is probably not worth the effort).
668 Re-do calls to signal() in remote.c, and inflow.c (set_sigint_trap and
669 so on) to be independent of the debugging target, using target_stop to
670 stop the inferior. Probably the part which is now handled by
671 interrupt_query in remote.c can be done without any new features in
672 the debugging target.
674 New test case based on weird.exp but in which type numbers are not
675 renumbered (thus multiply defining a type). This currently causes an
676 infinite loop on "p v_comb".
682 "source file more recent" loses on re-read
684 Fix 386 floating point so that floating point registers are real
685 registers (but code can deal at run-time if they are missing, like
686 mips and 68k). This would clean up "info float" and related stuff.
688 Look at Solaris bug in interrupt.exp. Can get out of syscall with
689 PRSABORT (syscall will return EINTR) but merely doing that leads to a
690 "can't read memory" error.
692 gcc -g -c enummask.c then gdb enummask.o, then "p v". GDB complains
693 about not being able to access memory location 0.
695 -------------------- enummask.c
714 If try to modify value in file with "set write off" should give
715 appropriate error not "cannot access memory at address 0x65e0".
717 Why do we allow a target to omit standard register names (NO_STD_REGS
718 in tm-z8k.h)? I thought the standard register names were supposed to
719 be just that, standard.
721 Allow core file without exec file on RS/6000.
723 Make sure "shell" with no arguments works right on DOS.
725 Make gdb.ini (as well as .gdbinit) be checked on all platforms, so
726 the same directory can be NFS-mounted on unix or DOS, and work the
729 cd ~/tmp/<M-?> causes infinite loop (where ~/tmp is a directory).
731 Get SECT_OFF_TEXT stuff out of objfile_relocate (might be needed to
732 get RS/6000 to work right, might not be immediately relevant).
734 Clean up add_toc_to_loadinfo
736 Think about attached processes and sharing terminal.
738 John sez in reference to ignoring errors from tcsegpgrp if attach_flag:
739 set_tty_state should not have any trouble with attached processes.
740 Instead, the tty handling should leave the pgrp of the tty alone when
741 attaching to processes (perhaps pass terminal_init_inferior a flag
742 saying whether we're attaching).
744 PAGE_SIZE redefined warnings on AIX. Probably should be using
745 BFD_PAGE_SIZE throughout BFD.
747 Rewrite proceed, wait_for_inferior, and normal_stop to clean them up.
750 1) Make each test in wait_for_inferior a seperate subroutine
752 2) Combine wait_for_inferior and normal_stop to clean up
753 communication via global variables.
754 3) See if you can find some way to clean up the global
755 variables that are used; possibly group them by data flow
756 and information content?
758 Work out some kind of way to allow running the inferior to be done as
759 a sub-execution of, eg. breakpoint command lists. Currently running
760 the inferior interupts any command list execution. This would require
761 some rewriting of wait_for_inferior & friends, and hence should
762 probably be done in concert with the above.
764 Add function arguments to gdb user defined functions.
766 Add convenience variables that refer to exec file, symbol file,
767 selected frame source file, selected frame function, selected frame
770 Add a "suspend" subcommand of the "continue" command to suspend gdb
771 while continuing execution of the subprocess. Useful when you are
772 debugging servers and you want to dodge out and initiate a connection
773 to a server running under gdb.
775 Add stab information to allow reasonable debugging of inline functions
776 (possibly they should show up on a stack backtrace? With a note
777 indicating that they weren't "real"?).
779 Modify the naked "until" command to step until past the current source
780 line, rather than past the current pc value. This is tricky simply
781 because the low level routines have no way of specifying a multi-line
782 step range, and there is no way of saying "don't print stuff when we
783 stop" from above (otherwise could just call step many times).
785 Modify the handling of symbols grouped through BINCL/EINCL stabs to
786 allocate a partial symtab for each BINCL/EINCL grouping. This will
787 seriously decrease the size of inter-psymtab dependencies and hence
788 lessen the amount that needs to be read in when a new source file is
791 Do an "x/i $pc" after each stepi or nexti.
793 Modify all of the disassemblers to use printf_filtered to get correct
796 Modify gdb to work correctly with Pascal.
798 Add a command for searching memory, a la adb. It specifies size,
799 mask, value, start address. ADB searches until it finds it or hits
800 an error (or is interrupted).
802 Remove the range and type checking code and documentation, if not