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