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