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