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