gdb/TODO

   1 If you find inaccuracies in this list, please send mail to
   2 gdb-patches@sourceware.cygnus.com.  If you would like to work on any
   3 of these, you should consider sending mail to the same address, to
   4 find out whether anyone else is working on it.
   5
   6
   7                 Known problems in GDB 5.0
   8                 =========================
   9
  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
  12 release.
  13
  14 --
  15
  16 The BFD directory requires bug-fixed AUTOMAKE et.al.
  17
  18 AUTOMAKE 1.4 incorrectly set the TEXINPUTS environment variable.  It
  19 contained the full path to texinfo.tex when it should have only
  20 contained the directory.  The bug has been fixed in the current
  21 AUTOMAKE sources.  Automake snapshots can be found in:
  22         ftp://sourceware.cygnus.com/pub/gdb/snapshots
  23 and     ftp://sourceware.cygnus.com/pub/binutils
  24
  25 --
  26
  27 RFD: infrun.c: No bpstat_stop_status call after proceed over break?
  28 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00665.html
  29
  30 GDB misses watchpoint triggers after proceeding over a breakpoint on
  31 x86 targets.
  32
  33 --
  34
  35 x86 linux GDB and SIGALRM (???)
  36 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00803.html
  37
  38 This problem has been fixed, but a regression test still needs to be
  39 added to the testsuite:
  40 http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00309.html
  41
  42 Mark
  43
  44 --
  45
  46 Revised UDP support (was: Re: [Fwd: [patch] UDP transport support])
  47 http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00000.html
  48
  49 (Broken) support for GDB's remote protocol across UDP is to be
  50 included in the follow-on release.
  51
  52 --
  53
  54 Can't build IRIX -> arm GDB.
  55 http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00356.html
  56
  57 David Whedon writes:
  58 > Now I'm building for an embedded arm target.  If there is a way of turning
  59 > remote-rdi off, I couldn't find it. It looks like it gets built by default
  60 > in gdb/configure.tgt(line 58) Anyway, the build dies in
  61 > gdb/rdi-share/unixcomm.c.  SERPORT1 et. al. never get defined because we
  62 > aren't one of the architectures supported.
  63
  64 --
  65
  66 Problem with weak functions
  67 http://sourceware.cygnus.com/ml/gdb/2000-05/msg00060.html
  68
  69 Dan Nicolaescu writes:
  70 > It seems that gdb-4.95.1  does not display correctly the function when
  71 > stoping in weak functions.
  72 >
  73 > It stops in a function that is defined as weak, not in the function
  74 > that is actualy run...
  75
  76 --
  77
  78 GDB 5.0 doesn't work on Linux/SPARC
  79
  80 --
  81
  82                 Code Cleanups: Next Release
  83                 ===========================
  84
  85 The following are small cleanups that will hopefully be completed by
  86 the follow on to 5.0.
  87
  88 --
  89
  90 Delete macro TARGET_BYTE_ORDER_SELECTABLE.
  91
  92 Patches in the database.
  93
  94 --
  95
  96 Purge PARAMS.
  97
  98 Eliminate all uses of PARAMS in GDB's source code.
  99
 100 --
 101
 102 Fix copyright notices.
 103
 104 Turns out that ``1998-2000'' isn't considered valid :-(
 105
 106 http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00467.html
 107
 108 --
 109
 110 Find something better than DEFAULT_BFD_ARCH, DEFAULT_BFD_VEC to
 111 determine the default isa/byte-order.
 112
 113 --
 114
 115 Rely on BFD_BIG_ENDIAN and BFD_LITTLE_ENDIAN instead of host dependant
 116 BIG_ENDIAN and LITTLE_ENDIAN.
 117
 118 --
 119
 120 printcmd.c (print_address_numeric):
 121
 122 NOTE: This assumes that the significant address information is kept in
 123 the least significant bits of ADDR - the upper bits were either zero
 124 or sign extended.  Should ADDRESS_TO_POINTER() or some
 125 ADDRESS_TO_PRINTABLE() be used to do the conversion?
 126
 127 --
 128
 129                 Code Cleanups: General
 130                 ======================
 131
 132 The following are more general cleanups and fixes.  They are not tied
 133 to any specific release.
 134
 135 --
 136
 137 Eliminate more compiler warnings.
 138
 139 Of course there also needs to be the usual debate over which warnings
 140 are valid and how to best go about this.
 141
 142 One method: choose a single option; get agreement that it is
 143 reasonable; try it out to see if there isn't anything silly about it
 144 (-Wunused-parameters is an example of that) then incrementally hack
 145 away.
 146
 147 The other method is to enable all warnings and eliminate them from one
 148 file at a time.
 149
 150 --
 151
 152 Elimination of ``(catch_errors_ftype *) func''.
 153
 154 Like make_cleanup_func it isn't portable.
 155 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00791.html
 156 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00814.html
 157
 158
 159 --
 160
 161 Nuke USG define.
 162
 163 --
 164
 165 [PATCH/5] src/intl/Makefile.in:distclean additions
 166 http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00363.html
 167
 168 Do not forget to merge the patch back into the trunk.
 169
 170 --
 171
 172 Rationalize the host-endian code (grep for HOST_BYTE_ORDER).
 173
 174 At present defs.h includes <endian.h> (which is linux specific) yet
 175 almost nothing depends on it.  Suggest "gdb_endian.h" which can also
 176 handle <machine/endian.h> and only include that where it is really
 177 needed.
 178
 179 --
 180
 181 Replace asprintf() calls with xasprintf() calls.
 182
 183 As with things like strdup() most calls to asprintf() don't check the
 184 return value.
 185
 186 --
 187
 188 Replace strsave() + mstrsave() with libiberty:xstrdup().
 189
 190 --
 191
 192 Replace savestring() with something from libiberty.
 193
 194 An xstrldup()? but that would have different semantics.
 195
 196 --
 197
 198 Rationalize use of floatformat_unknown in GDB sources.
 199
 200 Instead of defaulting to floatformat_unknown, should hosts/targets
 201 specify the value explicitly?
 202
 203 http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00447.html
 204
 205 --
 206
 207 Add a ``name'' member to include/floatformat.h:struct floatformat.
 208 Print that name in gdbarch.c.
 209
 210 --
 211
 212 Sort out the harris mess in include/floatformat.h (it hardwires two
 213 different floating point formats).
 214
 215 --
 216
 217 See of the GDB local floatformat_do_doublest() and libiberty's
 218 floatformat_to_double (which was once GDB's ...) can be merged some
 219 how.
 220
 221 --
 222
 223 Eliminate mmalloc() from GDB.
 224
 225 Also eliminate it from defs.h.
 226
 227 --
 228
 229 Eliminate PTR.  ISO-C allows ``void *''.
 230
 231 --
 232
 233 Eliminate abort ().
 234
 235 GDB should never abort.  GDB should either throw ``error ()'' or
 236 ``internal_error ()''.  Better still GDB should naturally unwind with
 237 an error status.
 238
 239 --
 240
 241 GDB probably doesn't build on FreeBSD pre 2.2.x
 242 http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00378.html
 243
 244 Fixes to get FreeBSD working on 2.2.x, 3.x and 4.x caused the code to
 245 suffer bit rot.
 246
 247 --
 248
 249 Deprecate "fg".  Apparently ``fg'' is actually continue.
 250
 251 http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00417.html
 252
 253 --
 254
 255 Deprecate current use of ``floatformat_unknown''.
 256
 257 Require all targets to explicitly provide their float format instead
 258 of defaulting to floatformat unknown.  Doing the latter leads to nasty
 259 bugs.
 260
 261 http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00447.html
 262
 263 --
 264
 265 Rationalize floatformat_to_double() vs floatformat_to_doublest().
 266
 267 Looks like GDB migrated floatformat_to_double() to libiberty but then
 268 turned around and created a ..._to_doublest() the latter containing
 269 several bug fixes.
 270
 271 http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00472.html
 272
 273 --
 274
 275 Move floatformat_ia64_ext to libiberty/include floatformat.[ch].
 276
 277 http://sourceware.cygnus.com/ml/gdb-patches/2000-05/msg00466.html
 278
 279 --
 280
 281 Follow through `make check' with --enable-shared.
 282
 283 When the srcware tree is configured with --enable-shared, the `expect'
 284 program won't run properly.  Jim Wilson found out gdb has a local hack
 285 to set LD_LIBRARY_PATH, but, AFAIK, no other project has been hacked
 286 similarly.
 287
 288 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00845.html
 289
 290 --
 291
 292 The ``maintenance deprecate set endian big'' command doesn't notice
 293 that it is deprecating ``set endian'' and not ``set endian big'' (big
 294 is implemented using an enum).  Is anyone going to notice this?
 295
 296 --
 297
 298 When tab expanding something like ``set arch<tab>'' ignore the
 299 deprecated ``set archdebug'' and expand to ``set architecture''.
 300
 301 --
 302
 303 Eliminate ``arm_register_names[j] = (char *) regnames[j]'' and the
 304 like from arm-tdep.c.
 305
 306 --
 307
 308 Fix uses of ->function.cfunc = set_function().
 309
 310 The command.c code calls sfunc() when a set command.  Rather than
 311 change it suggest fixing the callback function so that it is more
 312 useful.  See:
 313
 314 http://sourceware.cygnus.com/ml/gdb-patches/2000-06/msg00062.html
 315
 316 See also ``Fix implementation of  ``target xxx''.'' below.
 317
 318 --
 319
 320 IRIX 3.x support is probably broken.
 321
 322 --
 323
 324 Delete sim/SIM_HAVE_BREAKPOINTS and gdb/SIM_HAS_BREAKPOINTS.
 325 http://sourceware.cygnus.com/ml/gdb-patches/2000-07/msg00042.html
 326
 327 Apart from the d30v, are there any sim/common simulators that make use
 328 of this?
 329
 330 A brief summary of what happended is that sim/common/sim-break.c was
 331 created as a good idea.  It turned out a better idea was to use
 332 SIM_SIGBREAK and have GDB pass back sim_resume (..., SIGBREAK).
 333
 334 --
 335
 336 parse.c:build_parse() has a buffer overrun.
 337
 338 --
 339
 340                         New Features and Fixes
 341                         ======================
 342
 343 These are harder than cleanups but easier than work involving
 344 fundamental architectural change.
 345
 346 --
 347
 348 Add built-by, build-date, tm, xm, nm and anything else into gdb binary
 349 so that you can see how the GDB was created.
 350
 351 Some of these (*m.h) would be added to the generated config.h.  That
 352 in turn would fix a long standing bug where by the build process many
 353 not notice a changed tm.h file.  Since everything depends on config.h,
 354 a change to *m.h forces a change to config.h and, consequently forces
 355 a rebuild.
 356
 357 --
 358
 359 Add an "info bfd" command that displays supported object formats,
 360 similarly to objdump -i.
 361
 362 Is there a command already?
 363
 364 --
 365
 366 Fix ``I'm sorry, Dave, I can't do that.'' from symfile.c.
 367
 368 This requires internationalization.
 369
 370 --
 371
 372 Convert GDB build process to AUTOMAKE.
 373
 374 See also sub-directory configure below.
 375
 376 The current convention is (kind of) to use $(<header>_h) in all
 377 dependency lists.  It isn't done in a consistent way.
 378
 379 --
 380
 381 Cleanup configury support for optional sub-directories.
 382
 383 Check how GCC handles multiple front ends for an example of how things
 384 could work.  A tentative first step is to rationalize things so that
 385 all sub directories are handled in a fashion similar to gdb/mi.
 386
 387 See also automake above.
 388
 389 --
 390
 391 Restructure gdb directory tree so that it avoids any 8.3 and 14
 392 filename problems.
 393
 394 --
 395
 396 Add a transcript mechanism to GDB.
 397
 398 Such a mechanism might log all gdb input and output to a file in a
 399 form that would allow it to be replayed.  It could involve ``gdb
 400 --transcript=FILE'' or it could involve ``(gdb) transcript file''.
 401
 402 --
 403
 404 Can the xdep files be replaced by autoconf?
 405
 406 --
 407
 408 Document trace machinery
 409
 410 --
 411
 412 Document ui-out and ui-file.
 413
 414 http://sourceware.cygnus.com/ml/gdb/2000-04/msg00121.html
 415
 416 --
 417
 418 Update texinfo.tex to latest?
 419
 420
 421
 422 --
 423
 424 Incorporate agentexpr.texi into gdb.texinfo
 425
 426 agentexpr.texi mostly describes the details of the byte code used for
 427 tracepoints, not the internals of the support for this in GDB.  So it
 428 looks like gdb.texinfo is a better place for this information.
 429
 430 http://sourceware.cygnus.com/ml/gdb-patches/2000-04/msg00566.html
 431
 432 --
 433
 434 Document overlay machinery.
 435
 436 --
 437
 438 ``(gdb) catch signal SIGNAL''
 439
 440 Overlaps with ``handle SIGNAL'' but the implied behavour is different.
 441 You can attach commands to a catch but not a handle.  A handle has a
 442 limited number of hardwired actions.
 443
 444 --
 445
 446 Get the TUI working on all platforms.
 447
 448 --
 449
 450 Add support for ``gdb --- PROGRAM ARGS ...''.
 451 Add support for ``gdb -cmd=...''
 452
 453 Along with many variations.  Check:
 454
 455 ????? for a full discussion.
 456
 457 for a discussion.
 458
 459 --
 460
 461 Implement ``(gdb) !ls''.
 462
 463 Which is very different from ``(gdb) ! ls''.  Implementing the latter
 464 is trivial.
 465
 466 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00034.html
 467
 468 --
 469
 470 Change the (char *list[]) to (const char (*)[]) so that dynamic lists can
 471 be passed.
 472
 473 --
 474
 475 When tab expanding something like ``set arch<tab>'' ignore the
 476 deprecated ``set archdebug'' and expand to ``set architecture''.
 477
 478 --
 479
 480 Replace the code that uses the host FPU with an emulator of the target
 481 FPU.
 482
 483 --
 484
 485                         Thread Support
 486                         ==============
 487
 488 --
 489
 490 Generic: lin-thread cannot handle thread exit (Mark Kettenis, Michael
 491 Snyder) http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00525.html
 492
 493 The thread_db assisted debugging code doesn't handle exiting threads
 494 properly, at least in combination with glibc 2.1.3 (the framework is
 495 there, just not the actual code).  There are at least two problems
 496 that prevent this from working.
 497
 498 As an additional reference point, the pre thread_db code did not work
 499 either.
 500
 501 --
 502
 503 GNU/Linux/x86 and random thread signals (and Solaris/SPARC but not
 504 Solaris/x86).
 505 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00336.html
 506
 507 Christopher Blizzard writes:
 508
 509 So, I've done some more digging into this and it looks like Jim
 510 Kingdon has reported this problem in the past:
 511
 512 http://sourceware.cygnus.com/ml/bug-gdb/1999-10/msg00058.html
 513
 514 I can reproduce this problem both with and without Tom's patch.  Has
 515 anyone seen this before?  Maybe have a solution for it hanging around?
 516 :)
 517
 518 There's a test case for this documented at:
 519
 520 when debugging threaded applications you get extra SIGTRAPs
 521 http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=9565
 522
 523 [There should be a GDB testcase - cagney]
 524
 525 --
 526
 527 GDB5 TOT on unixware 7
 528 http://sourceware.cygnus.com/ml/gdb/2000-04/msg00119.html
 529
 530 Robert Lipe writes:
 531 > I just spun the top of tree of the GDB5 branch on UnixWare 7.  As a
 532 > practical matter, the current thread support is somewhat more annoying
 533 > than when GDB was thread-unaware.
 534
 535 --
 536
 537 Migrate qfThreadInfo packet -> qThreadInfo. (Andrew Cagney)
 538
 539 Add support for packet enable/disable commands with these thread
 540 packets.  General cleanup.
 541
 542 [PATCH] Document the ThreadInfo remote protocol queries
 543 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00832.html
 544
 545 [PATCH] "info threads" queries for remote.c
 546 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00831.html
 547
 548 --
 549
 550                         Language Support
 551                         ================
 552
 553 New languages come onto the scene all the time.
 554
 555 --
 556
 557 Pascal (Pierre Muller, David Taylor)
 558
 559 Pierre Muller has contributed patches for adding Pascal Language
 560 support to GDB.
 561
 562 2 pascal language patches inserted in database
 563 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00521.html
 564
 565 Indent -gnu ?
 566 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00496.html
 567
 568 --
 569
 570 Java (Anthony Green, David Taylor)
 571
 572 Anthony Green has a number of Java patches that did not make it into
 573 the 5.0 release.
 574
 575 Patch: java tests
 576 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00512.html
 577
 578 Patch: java booleans
 579 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00515.html
 580
 581 Patch: handle N_MAIN stab
 582 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00527.html
 583
 584 --
 585
 586 [Comming...]
 587
 588 Modify gdb to work correctly with Pascal.
 589
 590 --
 591
 592 Re: Various C++ things
 593
 594 value_headof/value_from_vtable_info are worthless, and should be
 595 removed.  The one place in printcmd.c that uses it should use the RTTI
 596 functions.
 597
 598 RTTI for g++ should be using the typeinfo functions rather than the
 599 vtables.  The typeinfo functions are always at offset 4 from the
 600 beginning of the vtable, and are always right. The vtables will have
 601 weird names like E::VB sometimes.  The typeinfo function will always
 602 be "E type_info function", or somesuch.
 603
 604 value_virtual_fn_field needs to be fixed so there are no failures for
 605 virtual functions for C++ using g++.
 606
 607 Testsuite cases are the major priority right now for C++ support,
 608 since i have to make a lot of changes that could potentially break
 609 each other.
 610
 611 --
 612
 613 Add support for Modula3
 614
 615 Get DEC/Compaq to contribute their Modula-3 support.
 616
 617 --
 618
 619                 Remote Protocol Support
 620                 =======================
 621
 622 --
 623
 624 set/show remote X-packet ...
 625
 626 ``(gdb) help set remote X-packet'' doesn't list the applicable
 627 responses.  The help message needs to be expanded.
 628
 629 --
 630
 631 Remote protocol doco feedback.
 632
 633 Too much feedback to mention needs to be merged in (901660).  Search
 634 for the word ``remote''.
 635
 636
 637 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00023.html
 638 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00056.html
 639 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00382.html
 640
 641 --
 642
 643 GDB doesn't recover gracefully from remote protocol errors.
 644
 645 GDB wasn't checking for NAKs from the remote target.  Instead a NAK is
 646 ignored and a timeout is required before GDB retries.  A pre-cursor to
 647 fixing this this is making GDB's remote protocol packet more robust.
 648
 649 While downloading to a remote protocol target, gdb ignores packet
 650 errors in so far as it will continue to edownload with chunk N+1 even
 651 if chunk N was not correctly sent.  This causes gdb.base/remote.exp to
 652 take a painfully long time to run.  As a PS that test needs to be
 653 fixed so that it builds on 16 bit machines.
 654
 655 --
 656
 657 Add the cycle step command.
 658
 659 http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00237.html
 660
 661 --
 662
 663 Resolve how to scale things to support very large packets.
 664
 665 --
 666
 667 Resolve how to handle a target that changes things like its endianess
 668 on the fly - should it be returned in the ``T'' packet?
 669
 670 Underlying problem is that the register file is target endian.  If the
 671 target endianess changes gdb doesn't know.
 672
 673 --
 674
 675                         Symbol Support
 676                         ==============
 677
 678 If / when GDB starts to support the debugging of multi-processor
 679 (rather than multi-thread) applications the symtab code will need to
 680 be updated a little so that several independant symbol tables are
 681 active at a given time.
 682
 683 The other interesting change is a clarification of the exact meaning
 684 of CORE_ADDR and that has had consequences for a few targets (that
 685 were abusing that data type).
 686
 687 --
 688
 689 Investiagate ways of reducing memory.
 690
 691 --
 692
 693 Investigate ways of improving load time.
 694
 695 --
 696
 697 Get the d10v to use POINTER_TO_ADDRESS and ADDRESS_TO_POINTER.
 698
 699 Consequence of recent symtab clarification.  No marks for figuring out
 700 who maintains the d10v.
 701
 702 --
 703
 704 Get the MIPS to correctly sign extend all address <-> pointer
 705 conversions.
 706
 707 Consequence of recent symtab clarification.  No marks for figuring out
 708 who maintains the MIPS.
 709
 710 --
 711
 712 GDB truncates 64 bit enums.
 713
 714 http://sourceware.cygnus.com/ml/gdb-patches/2000-06/msg00290.html
 715
 716 --
 717
 718                         Testsuite Support
 719                         =================
 720
 721 There are never to many testcases.
 722
 723 --
 724
 725 Better thread testsuite.
 726
 727 --
 728
 729 Better C++ testsuite.
 730
 731 --
 732
 733 Look at adding a GDB specific testsuite directory so that white box
 734 tests of key internals can be added (eg ui_file).
 735
 736 --
 737
 738 Separate out tests that involve the floating point (FP).
 739
 740 (Something for people brining up new targets).  FP and non-fp tests
 741 are combined.  I think there should be set of basic tests that
 742 exercise pure integer support and then a more expanded set that
 743 exercise FP and FP/integer interactions.
 744
 745 As an example, the MIPS, for n32 as problems with passing FP's and
 746 structs.  Since most inferior call tests include FP it is difficult to
 747 determine of the integer tests are ok.
 748
 749 --
 750
 751                 Architectural Changes: General
 752                 ==============================
 753
 754 These are harder than simple cleanups / fixes and, consequently
 755 involve more work.  Typically an Architectural Change will be broken
 756 down into a more digestible set of cleanups and fixes.
 757
 758 --
 759
 760 Cleanup software single step.
 761
 762 At present many targets implement software single step by directly
 763 blatting memory (see rs6000-tdep.c).  Those targets should register
 764 the applicable breakpoints using the breakpoint framework.  Perhaphs a
 765 new internal breakpoint class ``step'' is needed.
 766
 767 --
 768
 769 Replace READ_FP() with FRAME_HANDLE().
 770
 771 READ_FP() is a hangover from the days of the vax when the ABI really
 772 did have a frame pointer register.  Modern architectures typically
 773 construct a virtual frame-handle from the stack pointer and various
 774 other bits of string.
 775
 776 Unfortunatly GDB still treats this synthetic FP register as though it
 777 is real.  That in turn really confuses users (arm and ``print $fp'' VS
 778 ``info registers fp'').  The synthetic FP should be separated out of
 779 the true register set presented to the user.
 780
 781 --
 782
 783 Register Cache Cleanup (below from Andrew Cagney)
 784
 785 I would depict the current register architecture as something like:
 786
 787         High GDB  -->   Low GDB
 788             |              |
 789            \|/            \|/
 790             --- REG NR -----
 791                    |
 792     register + REGISTER_BYTE(reg_nr)
 793                    |
 794                   \|/
 795         -------------------------
 796         |  extern register[]    |
 797         -------------------------
 798
 799 where neither the high (valops.c et.al.) or low gdb (*-tdep.c) are
 800 really clear on what mechanisms they should be using to manipulate that
 801 buffer.   Further, much code assumes, dangerously, that registers are
 802 contigious.  Having got mips-tdep.c to support multiple ABIs, believe
 803 me, that is a bad assumption.  Finally, that register cache layout is
 804 determined by the current remote/local target and _not_ the less
 805 specific target ISA.  In fact, in many cases it is determined by the
 806 somewhat arbitrary layout of the [gG] packets!
 807
 808
 809 How I would like the register file to work is more like:
 810
 811
 812           High GDB
 813              |
 814             \|/
 815        pseudo reg-nr
 816              |
 817         map pseudo <->
 818         random cache
 819         bytes
 820              |
 821             \|/
 822         ------------
 823         | register |
 824         |  cache   |
 825         ------------
 826             /|\
 827              |
 828         map random cache
 829         bytes to target
 830         dependant i-face
 831             /|\
 832              |
 833        target dependant
 834         such as [gG] packet
 835         or ptrace buffer
 836
 837 The main objectives being:
 838
 839         o       a clear separation between the low
 840                 level target and the high level GDB
 841
 842         o       a mechanism that solves the general
 843                 problem of register aliases, overlaps
 844                 etc instead of treating them as optional
 845                 extras that can be wedged in as an after
 846                 thought (that is a reasonable description
 847                 of the current code).
 848
 849                 Identify then solve the hard case and the
 850                 rest just falls out.  GDB solved the easy
 851                 case and then tried to ignore the real
 852                 world :-)
 853
 854         o       a removal of the assumption that the
 855                 mapping between the register cache
 856                 and virtual registers is largely static.
 857                 If you flip the USR/SSR stack register
 858                 select bit in the status-register then
 859                 the corresponding stack registers should
 860                 reflect the change.
 861
 862         o       a mechanism that clearly separates the
 863                 gdb internal register cache from any
 864                 target (not architecture) dependant
 865                 specifics such as [gG] packets.
 866
 867 Of course, like anything, it sounds good in theory.  In reality, it
 868 would have to contend with many<->many relationships at both the
 869 virt<->cache and cache<->target level.  For instance:
 870
 871         virt<->cache
 872                 Modifying an mmx register may involve
 873                 scattering values across both FP and
 874                 mmpx specific parts of a buffer
 875
 876         cache<->target
 877                 When writing back a SP it may need to
 878                 both be written to both SP and USP.
 879
 880
 881 Hmm,
 882
 883 Rather than let this like the last time it was discussed, just slip, I'm
 884 first going to add this e-mail (+ references) to TODO.  I'd then like to
 885 sketch out a broad strategy I think could get us there.
 886
 887
 888 First thing I'd suggest is separating out the ``extern registers[]''
 889 code so that we can at least identify what is using it.  At present
 890 things are scattered across many files.  That way we can at least
 891 pretend that there is a cache instead of a global array :-)
 892
 893 I'd then suggest someone putting up a proposal for the pseudo-reg /
 894 high-level side interface so that code can be adopted to it.  For old
 895 code, initially a blanket rename of write_register_bytes() to
 896 deprecated_write_register_bytes() would help.
 897
 898 Following that would, finaly be the corresponding changes to the target.
 899
 900 --
 901
 902 Check that GDB can handle all BFD architectures (Andrew Cagney)
 903
 904 There should be a test that checks that BFD/GDB are in sync with
 905 regard to architecture changes.  Something like a test that first
 906 queries GDB for all supported architectures and then feeds each back
 907 to GDB..  Anyone interested in learning how to write tests?  :-)
 908
 909 --
 910
 911                 Architectural Change: Multi-arch et al.
 912                 =======================================
 913
 914 The long term objective is to remove all assumptions that there is a
 915 single target with a single address space with a single instruction
 916 set architecture and single application binary interface.
 917
 918 This is an ongoing effort.  The first milestone is to enable
 919 ``multi-arch'' where by all architectural decisions are made at
 920 runtime.
 921
 922 It should be noted that ``gdbarch'' is really ``gdbabi'' and
 923 ``gdbisa''.  Once things are multi-arched breaking that down correctly
 924 will become much easier.
 925
 926 --
 927
 928 GDBARCH cleanup (Andrew Cagney)
 929
 930 The non-generated parts of gdbarch.{sh,h,c} should be separated out
 931 into arch-utils.[hc].
 932
 933 Document that gdbarch_init_ftype could easily fail because it didn't
 934 identify an architecture.
 935
 936 --
 937
 938 Fix BELIEVE_PPC_PROMOTION.  Change it to BELIEVE_PPC_PROMOTION_P?
 939
 940 At present there is still #ifdef BELIEVE_PPC_PROMOTION code in the
 941 symtab file.
 942
 943 --
 944
 945 Fix target_signal_from_host() etc.
 946
 947 The name is wrong for starters.  ``target_signal'' should probably be
 948 ``gdb_signal''.  ``from_host'' should be ``from_target_signal''.
 949 After that it needs to be multi-arched and made independant of any
 950 host signal numbering.
 951
 952 --
 953
 954 Update ALPHA so that it uses ``struct frame_extra_info'' instead of
 955 EXTRA_FRAME_INFO.
 956
 957 This is a barrier to replacing mips_extra_func_info with something
 958 that works with multi-arch.
 959
 960 --
 961
 962 Multi-arch  mips_extra_func_info.
 963
 964 This first needs the alpha to be updated so that it uses ``struct
 965 frame_extra_info''.
 966
 967 --
 968
 969 Rationalize TARGET_SINGLE_FORMAT and TARGET_SINGLE_BIT et al.
 970
 971 Surely one of them is redundant.
 972
 973 --
 974
 975 Convert ALL architectures to MULTI-ARCH.
 976
 977 --
 978
 979 Select the initial multi-arch ISA / ABI based on --target or similar.
 980
 981 At present the default is based on what ever is first in the BFD
 982 archures table.  It should be determined based on the ``--target=...''
 983 name.
 984
 985 --
 986
 987 Make MIPS pure multi-arch.
 988
 989 It is only at the multi-arch enabled stage.
 990
 991 --
 992
 993 Truly multi-arch.
 994
 995 Enable the code to recognize --enable-targets=.... like BINUTILS does.
 996
 997 Can the tm.h and nm.h files be eliminated by multi-arch.
 998
 999 --
1000
1001         Architectural Change: MI, LIBGDB and scripting languages
1002         ========================================================
1003
1004 See also architectural changes related to the event loop.  LIBGDB
1005 can't be finished until there is a generic event loop being used by
1006 all targets.
1007
1008 The long term objective is it to be possible to integrate GDB into
1009 scripting languages.
1010
1011 --
1012
1013 Implement generic ``(gdb) commmand > file''
1014
1015 Once everything is going through ui_file it should be come fairly
1016 easy.
1017
1018 http://sourceware.cygnus.com/ml/gdb/2000-04/msg00104.html
1019
1020 --
1021
1022 Replace gdb_stdtarg with gdb_targout (and possibly gdb_targerr).
1023
1024 gdb_stdtarg is easily confused with gdb_stdarg.
1025
1026 --
1027
1028 Extra ui_file methods - dump.
1029
1030 Very useful for whitebox testing.
1031
1032 --
1033
1034 Eliminate error_begin().
1035
1036 With ui_file, there is no need for the statefull error_begin ()
1037 function.
1038
1039 --
1040
1041 Send normal output to gdb_stdout.
1042 Send error messages to gdb_stderror.
1043 Send debug and log output log gdb_stdlog.
1044
1045 GDB still contains many cases where (f)printf or printf_filtered () is
1046 used when it should be sending the messages to gdb_stderror or
1047 gdb_stdlog.  The thought of #defining printf to something has crossed
1048 peoples minds ;-)
1049
1050 --
1051
1052 Re-do GDB's output pager.
1053
1054 GDB's output pager still relies on people correctly using *_filtered
1055 for gdb_stdout and *_unfiltered for gdb_stdlog / gdb_stderr.
1056 Hopefully, with all normal output going to gdb_stdout, the pager can
1057 just look at the ui_file that the output is on and then use that to
1058 decide what to do about paging.  Sounds good in theory.
1059
1060 --
1061
1062 Check/cleanup MI documentation.
1063
1064 The list of commands specified in the documentation needs to be
1065 checked against the mi-cmds.c table in a mechanical way (so that they
1066 two can be kept up-to-date).
1067
1068 --
1069
1070 Convert MI into libgdb
1071
1072 MI provides a text interface into what should be many of the libgdb
1073 functions.  The implementation of those functions should be separated
1074 into the MI interface and the functions proper.  Those functions being
1075 moved to gdb/lib say.
1076
1077 --
1078
1079 Create libgdb.h
1080
1081 The first part can already be found in defs.h.
1082
1083 --
1084
1085 MI's input does not use buffering.
1086
1087 At present the MI interface reads raw characters of from an unbuffered
1088 FD.  This is to avoid several nasty buffer/race conditions.  That code
1089 should be changed so that it registers its self with the event loop
1090 (on the input FD) and then push commands up to MI as they arrive.
1091
1092 The serial code already does this.
1093
1094 --
1095
1096 Make MI interface accessable from existing CLI.
1097
1098 --
1099
1100 Add a breakpoint-edit command to MI.
1101
1102 It would be similar to MI's breakpoint create but would apply to an
1103 existing breakpoint.  It saves the need to delete/create breakpoints
1104 when ever they are changed.
1105
1106 --
1107
1108 Add directory path to MI breakpoint.
1109
1110 That way the GUI's task of finding the file within which the
1111 breakpoint was set is simplified.
1112
1113 --
1114
1115 Add a mechanism to reject certain expression classes to MI
1116
1117 There are situtations where you don't want GDB's expression
1118 parser/evaluator to perform inferior function calls or variable
1119 assignments.  A way of restricting the expression parser so that such
1120 operations are not accepted would be very helpful.
1121
1122 --
1123
1124 Remove sideffects from libgdb breakpoint create function.
1125
1126 The user can use the CLI to create a breakpoint with partial
1127 information - no file (gdb would use the file from the last
1128 breakpoint).
1129
1130 The libgdb interface currently affects that environment which can lead
1131 to confusion when a user is setting breakpoints via both the MI and
1132 the CLI.
1133
1134 This is also a good example of how getting the CLI ``right'' will be
1135 hard.
1136
1137 --
1138
1139 Move gdb_lasterr to ui_out?
1140
1141 The way GDB throws errors and records them needs a re-think.  ui_out
1142 handles the correct output well.  It doesn't resolve what to do with
1143 output / error-messages when things go wrong.
1144
1145 --
1146
1147 do_setshow_command contains a 1024 byte buffer.
1148
1149 The function assumes that there will never be any more than 1024 bytes
1150 of enum.  It should use mem_file.
1151
1152 --
1153
1154 Should struct cmd_list_element . completer take the command as an
1155 argument?
1156
1157 --
1158
1159 Should the bulk of top.c:line_completion_function() be moved to
1160 command.[hc]?  complete_on_cmdlist() and complete_on_enums() could
1161 then be made private.
1162
1163 --
1164
1165 top.c (execute_command): Should a command being valid when the target
1166 is running be made an attribute (predicate) to the command rather than
1167 an explicit set of tests.
1168
1169 --
1170
1171 top.c (execute_command): Should the bulk of this function be moved
1172 into command.[hc] so that top.c doesn't grub around in the command
1173 internals?
1174
1175 --
1176
1177                 Architectural Change: Async
1178                 ===========================
1179
1180 While GDB uses an event loop when prompting the user for input.  That
1181 event loop is not exploited by targets when they allow the target
1182 program to continue.  Typically targets still block in (target_wait())
1183 until the program again halts.
1184
1185 The closest a target comes to supporting full asynchronous mode are
1186 the remote targets ``async'' and ``extended-async''.
1187
1188 --
1189
1190 Asynchronous expression evaluator
1191
1192 Inferior function calls hang GDB.
1193
1194 --
1195
1196 Fix implementation of  ``target xxx''.
1197
1198 At present when the user specifies ``target xxxx'', the CLI maps that
1199 directly onto a target open method.  It is then assumed that the
1200 target open method should do all sorts of complicated things as this
1201 is the only chance it has.  Check how the various remote targets
1202 duplicate the target operations.  Check also how the various targets
1203 behave differently for purely arbitrary reasons.
1204
1205 What should happen is that ``target xxxx'' should call a generic
1206 ``target'' function and that should then co-ordinate the opening of
1207 ``xxxx''.  This becomes especially important when you're trying to
1208 open an asynchronous target that may need to perform background tasks
1209 as part of the ``attach'' phase.
1210
1211 Unfortunatly, due to limitations in the old/creaking command.h
1212 interface, that isn't possible.  The function being called isn't told
1213 of the ``xxx'' or any other context information.
1214
1215 Consequently a precursor to fixing ``target xxxx'' is to clean up the
1216 CLI code so that it passes to the callback function (attatched to a
1217 command) useful information such as the actual command and a context
1218 for that command.  Other changes such as making ``struct command''
1219 opaque may also help.
1220
1221 See also:
1222 http://sourceware.cygnus.com/ml/gdb-patches/2000-06/msg00062.html
1223
1224 --
1225
1226 Make "target xxx" command interruptible.
1227
1228 As things become async this becomes possible.  A target would start
1229 the connect and then return control to the event loop.  A cntrl-c
1230 would notify the target that the operation is to be abandoned and the
1231 target code could respond.
1232
1233 --
1234
1235 Add a "suspend" subcommand of the "continue" command to suspend gdb
1236 while continuing  execution of the subprocess.  Useful when you are
1237 debugging servers and you want to dodge out and initiate a connection
1238 to a server running under gdb.
1239
1240 [hey async!!]
1241
1242 --
1243
1244                         TODO FAQ
1245                         ========
1246
1247 Frequently requested but not approved requests.
1248
1249 --
1250
1251 Eliminate unused argument warnings using ATTRIBUTE_UNUSED.
1252
1253 The benefits on this one are thought to be marginal - GDBs design
1254 means that unused parameters are very common.  GCC 3.0 will also
1255 include the option -Wno-unused-parameter which means that ``-Wall
1256 -Wno-unused-parameters -Werror'' can be specified.
1257
1258 --
1259
1260
1261
1262                         Legacy Wish List
1263                         ================
1264
1265 This list is not up to date, and opinions vary about the importance or
1266 even desirability of some of the items.  If you do fix something, it
1267 always pays to check the below.
1268
1269 --
1270
1271 @c This does not work (yet if ever).  FIXME.
1272 @c @item --parse=@var{lang} @dots{}
1273 @c Configure the @value{GDBN} expression parser to parse the listed languages.
1274 @c @samp{all} configures @value{GDBN} for all supported languages.  To get a
1275 @c list of all supported languages, omit the argument.  Without this
1276 @c option, @value{GDBN} is configured to parse all supported languages.
1277
1278 --
1279
1280 START_INFERIOR_TRAPS_EXPECTED need never be defined to 2, since that
1281 is its default value.  Clean this up.
1282
1283 --
1284
1285 It should be possible to use symbols from shared libraries before we know
1286 exactly where the libraries will be loaded.  E.g. "b perror" before running
1287 the program.  This could maybe be done as an extension of the "breakpoint
1288 re-evaluation" after new symbols are loaded.
1289
1290 --
1291
1292 Make single_step() insert and remove breakpoints in one operation.
1293
1294 [If this is talking about having single_step() insert the breakpoints,
1295 run the target then pull the breakpoints then it is wrong.  The
1296 function has to return as control has to eventually be passed back to
1297 the main event loop.]
1298
1299 --
1300
1301 Speed up single stepping by avoiding extraneous ptrace calls.
1302
1303 --
1304
1305 Speed up single stepping by not inserting and removing breakpoints
1306 each time the inferior starts and stops.
1307
1308 Breakpoints should not be inserted and deleted all the time.  Only the
1309 one(s) there should be removed when we have to step over one.  Support
1310 breakpoints that don't have to be removed to step over them.
1311
1312 [this has resulted in numerous debates.  The issue isn't clear cut]
1313
1314 --
1315
1316 Provide "voodoo" debugging of core files.  This creates a zombie
1317 process as a child of the debugger, and loads it up with the data,
1318 stack, and regs of the core file.  This allows you to call functions
1319 in the executable, to manipulate the data in the core file.
1320
1321 [you wish]
1322
1323 --
1324
1325 GDB reopens the source file on every line, as you "next" through it.
1326
1327 [still true? I've a memory of this being fixed]
1328
1329 --
1330
1331 Perhaps "i source" should take an argument like that of "list".
1332
1333 --
1334
1335 Remove "at 0xnnnn" from the "b foo" response, if `print address off' and if
1336 it matches the source line indicated.
1337
1338 --
1339
1340 The prompt at end of screen should accept space as well as CR.
1341
1342 --
1343
1344 Backtrace should point out what the currently selected frame is, in
1345 its display, perhaps showing "@3 foo (bar, ...)" or ">3 foo (bar,
1346 ...)" rather than "#3 foo (bar, ...)".
1347
1348 --
1349
1350 "i program" should work for core files, and display more info, like what
1351 actually caused it to die.
1352
1353 --
1354
1355 "x/10i" should shorten the long name, if any, on subsequent lines.
1356
1357 --
1358
1359 "next" over a function that longjumps, never stops until next time you happen
1360 to get to that spot by accident.  E.g. "n" over execute_command which has
1361 an error.
1362
1363 --
1364
1365 "set zeroprint off", don't bother printing members of structs which
1366 are entirely zero.  Useful for those big structs with few useful
1367 members.
1368
1369 --
1370
1371 GDB does four ioctl's for every command, probably switching terminal modes
1372 to/from inferior or for readline or something.
1373
1374 --
1375
1376 terminal_ours versus terminal_inferior: cache state.  Switch should be a noop
1377 if the state is the same, too.
1378
1379 --
1380
1381 "i frame" shows wrong "arglist at" location, doesn't show where the args
1382 should be found, only their actual values.
1383
1384 --
1385
1386 There should be a way for "set" commands to validate the new setting
1387 before it takes effect.
1388
1389 --
1390
1391 "ena d" is ambiguous, why?  "ena delete" seems to think it is a command!
1392
1393 --
1394
1395 i line VAR produces "Line number not known for symbol ``var''.".  I
1396 thought we were stashing that info now!
1397
1398 --
1399
1400 We should be able to write to random files at hex offsets like adb.
1401
1402 --
1403
1404 [elena - delete this]
1405
1406 Handle add_file with separate text, data, and bss addresses.  Maybe
1407 handle separate addresses for each segment in the object file?
1408
1409 --
1410
1411 [Jimb/Elena delete this one]
1412
1413 Handle free_named_symtab to cope with multiply-loaded object files
1414 in a dynamic linking environment.  Should remember the last copy loaded,
1415 but not get too snowed if it finds references to the older copy.
1416
1417 --
1418
1419 [elena delete this also]
1420
1421 Remove all references to:
1422         text_offset
1423         data_offset
1424         text_data_start
1425         text_end
1426         exec_data_offset
1427         ...
1428 now that we have BFD.  All remaining are in machine dependent files.
1429
1430 --
1431
1432 Re-organize help categories into things that tend to fit on a screen
1433 and hang together.
1434
1435 --
1436
1437 Add in commands like ADB's for searching for patterns, etc.  We should
1438 be able to examine and patch raw unsymboled binaries as well in gdb as
1439 we can in adb.  (E.g. increase the timeout in /bin/login without source).
1440
1441 [actually, add ADB interface :-]
1442
1443 --
1444
1445 When doing "step" or "next", if a few lines of source are skipped between
1446 the previous line and the current one, print those lines, not just the
1447 last line of a multiline statement.
1448
1449 --
1450
1451 Handling of "&" address-of operator needs some serious overhaul
1452 for ANSI C and consistency on arrays and functions.
1453   For "float point[15];":
1454 ptype &point[4]   ==> Attempt to take address of non-lvalue.
1455   For "char *malloc();":
1456 ptype malloc      ==> "char *()";  should be same as
1457 ptype &malloc     ==> "char *(*)()"
1458 call printf ("%x\n", malloc)   ==> weird value, should be same as
1459 call printf ("%x\n", &malloc)  ==> correct value
1460
1461 --
1462
1463 Fix dbxread.c symbol reading in the presence of interrupts.  It
1464 currently leaves a cleanup to blow away the entire symbol table when a
1465 QUIT occurs.  (What's wrong with that? -kingdon, 28 Oct 1993).
1466
1467 [I suspect that the grype was that, on a slow system, you might want
1468 to cntrl-c and get just half the symbols and then load the rest later
1469 - scary to be honest]
1470
1471 --
1472
1473 Mipsread.c reads include files depth-first, because the dependencies
1474 in the psymtabs are way too inclusive (it seems to me).  Figure out what
1475 really depends on what, to avoid recursing 20 or 30 times while reading
1476 real symtabs.
1477
1478 --
1479
1480 value_add() should be subtracting the lower bound of arrays, if known,
1481 and possibly checking against the upper bound for error reporting.
1482
1483 --
1484
1485 When listing source lines, check for a preceding \n, to verify that
1486 the file hasn't changed out from under us.
1487
1488 [fixed by some other means I think.  That hack wouldn't actually work
1489 reliably - the file might move such that another \n appears. ]
1490
1491 --
1492
1493 Get all the remote systems (where the protocol allows it) to be able to
1494 stop the remote system when the GDB user types ^C (like remote.c
1495 does).  For ebmon, use ^Ak.
1496
1497 --
1498
1499 Possible feature: A version of the "disassemble" command which shows
1500 both source and assembly code ("set symbol-filename on" is a partial
1501 solution).
1502
1503 [has this been done?  It was certainly done for MI and GDBtk]
1504
1505 --
1506
1507 investigate "x/s 0" (right now stops early) (I think maybe GDB is
1508 using a 0 address for bad purposes internally).
1509
1510 --
1511
1512 Make "info path" and path_command work again (but independent of the
1513 environment either of gdb or that we'll pass to the inferior).
1514
1515 --
1516
1517 Make GDB understand the GCC feature for putting octal constants in
1518 enums.  Make it so overflow on an enum constant does not error_type
1519 the whole type.  Allow arbitrarily large enums with type attributes.
1520 Put all this stuff in the testsuite.
1521
1522 --
1523
1524 Make TYPE_CODE_ERROR with a non-zero TYPE_LENGTH more useful (print
1525 the value in hex; process type attributes).  Add this to the
1526 testsuite.  This way future compilers can add new types and old
1527 versions of GDB can do something halfway reasonable.
1528
1529 --
1530
1531 Fix mdebugread.c:parse_type to do fundamental types right (see
1532 rs6000_builtin_type in stabsread.c for what "right" is--the point is
1533 that the debug format fixes the sizes of these things and it shouldn't
1534 depend on stuff like TARGET_PTR_BIT and so on.  For mdebug, there seem
1535 to be separate bt* codes for 64 bit and 32 bit things, and GDB should
1536 be aware of that).  Also use a switch statement for clarity and speed.
1537
1538 --
1539
1540 Investigate adding symbols in target_load--some targets do, some
1541 don't.
1542
1543 --
1544
1545 Put dirname in psymtabs and change lookup*symtab to use dirname (so
1546 /foo/bar.c works whether compiled by cc /foo/bar.c, or cd /foo; cc
1547 bar.c).
1548
1549 --
1550
1551 Merge xcoffread.c and coffread.c.  Use breakpoint_re_set instead of
1552 fixup_breakpoints.
1553
1554 --
1555
1556 Make a watchpoint which contains a function call an error (it is
1557 broken now, making it work is probably not worth the effort).
1558
1559 --
1560
1561 New test case based on weird.exp but in which type numbers are not
1562 renumbered (thus multiply defining a type).  This currently causes an
1563 infinite loop on "p v_comb".
1564
1565 --
1566
1567 [Hey! Hint Hint Delete Delete!!!]
1568
1569 Fix 386 floating point so that floating point registers are real
1570 registers (but code can deal at run-time if they are missing, like
1571 mips and 68k).  This would clean up "info float" and related stuff.
1572
1573 --
1574
1575 gcc -g -c enummask.c then gdb enummask.o, then "p v".  GDB complains
1576 about not being able to access memory location 0.
1577
1578 -------------------- enummask.c
1579 enum mask
1580 {
1581   ANIMAL = 0,
1582   VEGETABLE = 1,
1583   MINERAL = 2,
1584   BASIC_CATEGORY = 3,
1585
1586   WHITE = 0,
1587   BLUE = 4,
1588   GREEN = 8,
1589   BLACK = 0xc,
1590   COLOR = 0xc,
1591
1592   ALIVE = 0x10,
1593
1594   LARGE = 0x20
1595 } v;
1596
1597 --
1598
1599 If try to modify value in file with "set write off" should give
1600 appropriate error not "cannot access memory at address 0x65e0".
1601
1602 --
1603
1604 Allow core file without exec file on RS/6000.
1605
1606 --
1607
1608 Make sure "shell" with no arguments works right on DOS.
1609
1610 --
1611
1612 Make gdb.ini (as well as .gdbinit) be checked on all platforms, so
1613 the same directory can be NFS-mounted on unix or DOS, and work the
1614 same way.
1615
1616 --
1617
1618 [Is this another delete???]
1619
1620 Get SECT_OFF_TEXT stuff out of objfile_relocate (might be needed to
1621 get RS/6000 to work right, might not be immediately relevant).
1622
1623 --
1624
1625 Work out some kind of way to allow running the inferior to be done as
1626 a sub-execution of, eg. breakpoint command lists.  Currently running
1627 the inferior interupts any command list execution.  This would require
1628 some rewriting of wait_for_inferior & friends, and hence should
1629 probably be done in concert with the above.
1630
1631 --
1632
1633 Add function arguments to gdb user defined functions.
1634
1635 --
1636
1637 Add convenience variables that refer to exec file, symbol file,
1638 selected frame source file, selected frame function, selected frame
1639 line number, etc.
1640
1641 --
1642
1643 Modify the handling of symbols grouped through BINCL/EINCL stabs to
1644 allocate a partial symtab for each BINCL/EINCL grouping.  This will
1645 seriously decrease the size of inter-psymtab dependencies and hence
1646 lessen the amount that needs to be read in when a new source file is
1647 accessed.
1648
1649 --
1650
1651 Add a command for searching memory, a la adb.  It specifies size,
1652 mask, value, start address.  ADB searches until it finds it or hits
1653 an error (or is interrupted).
1654
1655 --
1656
1657 Remove the range and type checking code and documentation, if not
1658 going to implement.
1659
1660 # Local Variables:
1661 # mode: text
1662 # End: