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