Commit | Line | Data |
---|---|---|
c906108c SS |
1 | If you find inaccuracies in this list, please send mail to |
2 | bug-gdb@prep.ai.mit.edu. If you would like to work on any of these, | |
3 | you should consider sending mail to the same address, to find out | |
4 | whether anyone else is working on it. | |
5 | ||
138f88c0 AC |
6 | |
7 | TODO: GDB 5.0 | |
8 | ============= | |
9 | ||
10 | Here are _all_ the issues that have been raised vis-a-vis the 5.0 | |
11 | release. Also check the GDB, and other, mail archives | |
12 | (http://sourceware.cygnus.com/ml/gdb/). | |
13 | ||
14 | If, however, you fix something, then feel free to tweek this file | |
15 | (deleting the problem). Just send a note to gdb-patches so that I see | |
16 | the change. | |
17 | ||
18 | The names in paren are those that might know more about the problem. | |
19 | They don't necessarily indicate the people that will fix the problem. | |
20 | ||
21 | -- | |
22 | ||
23 | GDB 5.0: Must have | |
c906108c SS |
24 | ------------------ |
25 | ||
138f88c0 AC |
26 | These are things that have been identifed as must-have for this |
27 | release of GDB. | |
28 | ||
29 | -- | |
30 | ||
31 | Watch point related patches (Eli Zaretskii, Michael Snyder, ???) | |
32 | ||
33 | Eli writes: This doesn't include the watchpoint-related patches I sent | |
34 | beginning with August or September, and mentioned them again three | |
35 | weeks ago. Here again are the pointers to the relevant messages: | |
36 | ||
37 | Hardware breakpoints and watchpoints: patches | |
38 | http://sourceware.cygnus.com/ml/gdb-patches/1999-q3/msg00173.html | |
39 | ||
40 | Re: Hardware breakpoints and watchpoints: patches | |
41 | http://sourceware.cygnus.com/ml/gdb-patches/1999-q3/msg00204.html | |
42 | ||
43 | Re: Hardware breakpoints and watchpoints: patches | |
44 | http://sourceware.cygnus.com/ml/gdb-patches/1999-q4/msg00200.html | |
45 | ||
46 | Hardware watchpoints for bitfields | |
47 | http://sourceware.cygnus.com/ml/gdb-patches/1999-q4/msg00201.html | |
48 | ||
49 | -- | |
50 | ||
51 | Tom's speedups to GDB (Tom Tromey, Jim Blandy) | |
52 | ||
53 | I believe that there was a late breaking fix that stopped a coredump. | |
54 | ||
55 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00869.html | |
56 | ||
57 | -- | |
58 | ||
59 | Solaris/x86 - which? (Nick Duffek, Peter Schauer, Michael Snyder?) | |
60 | ||
61 | Nick D's working through patches from Michael Snyder and Peter S. | |
62 | ||
63 | -- | |
64 | ||
138f88c0 | 65 | |
67edb2c6 AC |
66 | RFA: procfs.c: init_procfs_ops should set |
67 | procfs_ops.to_has_[all]_memory (Peter Schauer, Andrew Cagney?) | |
138f88c0 | 68 | |
67edb2c6 AC |
69 | I am pretty sure that this is caused by some accidental deletion, but |
70 | procfs.c:init_procfs_ops no longer sets procfs_ops.to_has_memory and | |
71 | procfs_ops.to_has_all_memory. | |
138f88c0 | 72 | |
67edb2c6 | 73 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg01057.html |
138f88c0 AC |
74 | |
75 | -- | |
76 | ||
77 | GDB 5.0: Nice to have | |
78 | --------------------- | |
79 | ||
80 | These are things that might make it in 5.0 but don't sit in the | |
81 | critical path. If they miss the 5.0 cut then they definitly should | |
82 | make the follow-on release. | |
83 | ||
84 | -- | |
85 | ||
86 | Generic: lin-thread cannot handle thread exit (Mark Kettenis, Michael Snyder) | |
87 | http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00525.html | |
88 | ||
89 | The thread_db assisted debugging code doesn't handle exiting threads | |
90 | properly, at least in combination with glibc 2.1.3 (the framework is | |
91 | there, just not the actual code). There are at least two problems | |
92 | that prevent this from working. | |
93 | ||
94 | As an additional reference point, the pre thread_db code didn't work | |
95 | either. | |
96 | ||
97 | -- | |
98 | ||
99 | Java (Anthony Green, David Taylor) | |
100 | ||
101 | Anthony Green has started contributing late breaking Java patches: | |
102 | ||
103 | Patch: java tests | |
104 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00512.html | |
105 | ||
106 | Patch: java booleans | |
107 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00515.html | |
108 | ||
109 | Patch: handle N_MAIN stab | |
110 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00527.html | |
111 | ||
112 | It should be able to squeeze these in. | |
113 | ||
114 | -- | |
115 | ||
116 | Pascal (Pierre Muller, David Taylor) | |
117 | ||
118 | The pascal support patches nave been added to the patch data base. I | |
119 | [cagney] strongly suspect that they are better suited for 5.1. | |
120 | ||
67edb2c6 AC |
121 | Indent -gnu ? |
122 | http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00496.html | |
123 | ||
124 | 2 pascal language patches inserted in database | |
125 | http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00521.html | |
126 | ||
138f88c0 AC |
127 | -- |
128 | ||
129 | Programs run under GDB have SIGCHLD masked. | |
130 | ||
131 | [I think this can be worked around by using the action command - | |
132 | cagney] | |
133 | ||
134 | -- | |
135 | ||
136 | GNU/Linux/x86 and random thread signals (and Solaris/SPARC but not | |
137 | Solaris/x86) | |
138 | ||
139 | Christopher Blizzard writes: | |
140 | ||
141 | So, I've done some more digging into this and it looks like Jim | |
142 | Kingdon has reported this problem in the past: | |
143 | ||
144 | http://sourceware.cygnus.com/ml/bug-gdb/1999-10/msg00058.html | |
145 | ||
146 | I can reproduce this problem both with and without Tom's patch. Has | |
147 | anyone seen this before? Maybe have a solution for it hanging around? | |
148 | :) | |
149 | ||
150 | There's a test case for this documented at: | |
151 | ||
152 | when debugging threaded applications you get extra SIGTRAPs | |
153 | http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=9565 | |
154 | ||
155 | [There should be a GDB testcase - cagney] | |
156 | ||
157 | -- | |
158 | ||
159 | IRIX? | |
160 | ||
161 | Benjamin Gamsa wrote: | |
162 | ||
163 | Has anyone successfully built the latest (from cvs) gdb on IRIX6.4 or | |
164 | later? The first problem I hit is that proc-api.c includes | |
165 | sys/user.h, which no longer exists under IRIX6.4. If I comment out | |
166 | that include, the next problem I hit is that PIOCGETPR and PIOCGETU | |
167 | are no longer defined in IRIX6.4 (presumably related to the | |
168 | disappearance of user.h). | |
169 | ||
170 | -- | |
171 | ||
172 | Regressions (prologue) with devel GCC. | |
173 | ||
174 | The current head of the GCC branch doesn't co-operate well with GDB | |
175 | over debug information. | |
176 | ||
177 | Regressions problem (200 failures) | |
178 | http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00475.html | |
179 | ||
180 | -- | |
181 | ||
182 | RFA: infrun.c, breakpoint.c: Kludge for Solaris x86 hardware watchpoint support | |
183 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00664.html | |
184 | ||
185 | Unfortunately I'd need the following kludge to work around a Solaris | |
186 | x86 kernel problem with hardware watchpoint support. See the comment | |
187 | in the patches for a description of the problem. | |
188 | ||
189 | -- | |
190 | ||
191 | RFD: infrun.c: No bpstat_stop_status call after proceed over break ? | |
192 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00665.html | |
193 | ||
194 | I am currently trying to fix a GDB bug with missing watchpoint triggers | |
195 | after proceeding over a breakpoint on x86 targets. | |
196 | ||
197 | -- | |
198 | ||
67edb2c6 AC |
199 | x86 linux GDB and SIGALRM (???) |
200 | http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00803.html | |
201 | ||
202 | -- | |
203 | ||
204 | Migrate qfThreadInfo packet -> qThreadInfo. (Andrew Cagney) | |
205 | ||
206 | Add support for packet enable/disable commands with these thread | |
207 | packets. General cleanup. | |
208 | ||
209 | [PATCH] Document the ThreadInfo remote protocol queries | |
210 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00832.html | |
211 | ||
212 | [PATCH] "info threads" queries for remote.c | |
213 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00831.html | |
214 | ||
215 | -- | |
216 | ||
217 | MI documentation in GDB user guide. (Andrew Cagney, Elena Zannoni, | |
218 | Stan Shebs, anyone else?) | |
219 | ||
220 | > (Are there plans to make gdbmi.texi be part of the manual as well?) | |
221 | ||
222 | I'd like to see it go in there sooner rather than later too. Otherwise | |
223 | you're introducing discrepancies between the manual and the documentation, | |
224 | and everybody is confused - witness the lack of doc for the tracing | |
225 | commands still, some two years after they were added... | |
226 | ||
227 | [PATCH] GDB command-line switches and annotations docs | |
228 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00639.html | |
229 | ||
230 | -- | |
231 | ||
138f88c0 AC |
232 | GDB 5.0: Won't have |
233 | ------------------- | |
234 | ||
235 | The following are on hold until GDB 5.0 is branched. In general they | |
236 | won't go in as they unsettle the GDB sources. | |
237 | ||
238 | -- | |
239 | ||
240 | ATTRIBUTE_UNUSED | |
241 | ||
242 | The need for this as almost been eliminated. The next version of GCC | |
243 | (assuming cagney gets the revised patch approved) will be able to | |
244 | supress unused parameter warnings. | |
245 | ||
246 | -- | |
247 | ||
248 | Delete macro TARGET_BYTE_ORDER_SELECTABLE. | |
249 | ||
250 | Patches in the database. | |
251 | ||
252 | -- | |
253 | ||
254 | Updated readline | |
255 | ||
256 | Readline 4.? is out. A merge wouldn't hurt. | |
257 | ||
258 | -- | |
259 | ||
260 | Purge PARAMS | |
261 | ||
262 | Something to do post 5.0 branch | |
263 | ||
264 | -- | |
265 | ||
67edb2c6 AC |
266 | Elimination of make_cleanup_func. (Andrew Cagney) |
267 | ||
268 | make_cleanup_func elimination | |
269 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00791.html | |
270 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00814.html | |
271 | ||
272 | -- | |
273 | ||
274 | Allow GDB to use installed regex. Think about updating regex to more | |
275 | recent version (Andrew Cagney). | |
276 | ||
277 | Re: A new patch for regex | |
278 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00635.html | |
279 | ||
280 | A patch for gnu-regex | |
281 | http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00568.html | |
282 | ||
283 | -- | |
284 | ||
285 | ChangeLog.mi vs ChangeLog-mi (Andrew Cagney) | |
286 | Needs further debate. | |
287 | ||
288 | Re: [PATCH] Add change-log variables to more MI files | |
289 | http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00811.html | |
290 | ||
291 | -- | |
292 | ||
138f88c0 AC |
293 | GDB 5.0: Test results |
294 | --------------------- | |
295 | ||
296 | Please include: | |
297 | ||
298 | o the output of `config.guess` | |
299 | o the date | |
300 | o the compiler | |
301 | o a note mentioning the reason | |
302 | for any serious failures. | |
303 | ||
304 | -- | |
305 | ||
306 | alpha-dec-osf4.0a, vendor compiler, 2000-03-04 | |
307 | ||
308 | Still has many compile warnings (mostly relating back to PTR vs void*) | |
309 | but it did compile using: | |
310 | ||
311 | CC=cc .../configure | |
312 | make | |
313 | ||
314 | Test results are: | |
315 | ||
316 | # of expected passes 6223 | |
317 | # of unexpected failures 103 | |
318 | # of unexpected successes 2 | |
319 | # of expected failures 196 | |
320 | # of unresolved testcases 6 | |
321 | # of unsupported tests 1 | |
322 | ||
323 | Looking at the output it would appear that GDB is stepping into some | |
324 | functions instead of ``next'' ing over them: | |
325 | ||
326 | 35 dummy(); | |
327 | (gdb) next | |
328 | dummy () at /home/cagney/GDB-DEJAGNU/src/gdb/testsuite/gdb.base/all-types.c:41 | |
329 | 41 { | |
330 | ||
331 | Since there is no active maintainer, I'd consider this sufficient for | |
332 | 5.0 :-/ | |
333 | ||
334 | -- | |
335 | ||
336 | sparc-sun-solaris2.6, egcs-2.91.66, 2000-02-10 | |
337 | http://sourceware.cygnus.com/ml/gdb-testers/2000-q1/msg00030.html | |
338 | ||
339 | There is a SIGTRAP problem that occures in ptrace.exp (Cagney to | |
340 | expand on). | |
341 | ||
342 | # of expected passes 6420 | |
343 | # of unexpected failures 7 | |
344 | # of expected failures 199 | |
345 | ||
346 | -- | |
347 | ||
348 | solaris 2.5.1 sparc?, 2.9-gnupro-99r1, 2000-02-10 | |
349 | http://sourceware.cygnus.com/ml/gdb-testers/2000-q1/msg00032.html | |
350 | ||
351 | # of expected passes 6420 | |
352 | # of unexpected failures 6 | |
353 | # of expected failures 199 | |
354 | ||
355 | -- | |
356 | ||
357 | sparc-unknown-netbsdelf1.4P, egcs-1.1.2+, 2000-03-01 | |
358 | ||
359 | This is with a very recent kernel. | |
360 | ||
361 | # of expected passes 6055 | |
362 | # of unexpected failures 88 | |
363 | # of unexpected successes 1 | |
364 | # of expected failures 190 | |
365 | # of unresolved testcases 59 | |
366 | ||
367 | -- | |
368 | ||
369 | GNU/Linux PPC | |
370 | http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00185.html | |
371 | ||
372 | Kevins merged it all in. | |
373 | ||
374 | -- | |
375 | ||
376 | Unixware | |
377 | ||
378 | Builds ok. Problems with some of the thread code. Unfortunate but | |
379 | not a show stopper. Nick D's still looking at it. | |
380 | ||
381 | Re: uw-threads issues | |
382 | http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00025.html | |
383 | ||
384 | ||
385 | ------------------------------------------------ | |
386 | ||
387 | ||
388 | General Wish List | |
389 | ================= | |
390 | ||
67edb2c6 AC |
391 | -- |
392 | ||
393 | GDBARCH cleanup (Andrew Cagney) | |
394 | ||
395 | The non-generated parts of gdbarch.{sh,h,c} should be separated out | |
396 | into gdbarch-utils.[hc] (Name ok). | |
397 | ||
398 | The ``info architecture'' command should be replaced with a fixed | |
399 | ``set architecture'' (implemented using the command.c enum code). | |
400 | ||
401 | Document that gdbarch_init_ftype could easily fail because it didn't | |
402 | identify an architecture. | |
403 | ||
404 | -- | |
405 | ||
406 | Check that GDB can handle all BFD architectures (Andrew Cagney) | |
407 | ||
408 | There should be a test that checks that BFD/GDB are in sync with | |
409 | regard to architecture changes. Something like a test that first | |
410 | queries GDB for all supported architectures and then feeds each back | |
411 | to GDB.. Anyone interested in learning how to write tests? :-) | |
412 | ||
413 | -- | |
414 | ||
c906108c SS |
415 | This list is probably not up to date, and opinions vary about the |
416 | importance or even desirability of some of the items. | |
417 | ||
b83266a0 SS |
418 | Document trace machinery. |
419 | ||
420 | Document overlay machinery. | |
421 | ||
422 | Extend .gdbinit mechanism to specify name on command line, allow for | |
423 | lists of files to load, include function of --tclcommand. | |
424 | ||
425 | @c This does not work (yet if ever). FIXME. | |
426 | @c @item --parse=@var{lang} @dots{} | |
427 | @c Configure the @value{GDBN} expression parser to parse the listed languages. | |
428 | @c @samp{all} configures @value{GDBN} for all supported languages. To get a | |
429 | @c list of all supported languages, omit the argument. Without this | |
430 | @c option, @value{GDBN} is configured to parse all supported languages. | |
431 | ||
c906108c SS |
432 | Add an "info bfd" command that displays supported object formats, |
433 | similarly to objdump -i. | |
434 | ||
435 | START_INFERIOR_TRAPS_EXPECTED need never be defined to 2, since that | |
436 | is its default value. Clean this up. | |
437 | ||
438 | It should be possible to use symbols from shared libraries before we know | |
439 | exactly where the libraries will be loaded. E.g. "b perror" before running | |
440 | the program. This could maybe be done as an extension of the "breakpoint | |
441 | re-evaluation" after new symbols are loaded. | |
442 | ||
443 | Make single_step() insert and remove breakpoints in one operation. | |
444 | ||
445 | Speed up single stepping by avoiding extraneous ptrace calls. | |
446 | ||
447 | Speed up single stepping by not inserting and removing breakpoints | |
448 | each time the inferior starts and stops. | |
449 | ||
450 | Breakpoints should not be inserted and deleted all the time. Only the | |
451 | one(s) there should be removed when we have to step over one. Support | |
452 | breakpoints that don't have to be removed to step over them. | |
453 | ||
454 | Update gdbint.texinfo to include doc on the directory structure and | |
455 | the various tricks of building gdb. | |
456 | ||
457 | Do a tutorial in gdb.texinfo on how to do simple things in gdb. | |
458 | E.g. how to set a breakpoint that just prints something and continues. | |
459 | How to break on aborts. Etc. | |
460 | ||
461 | Provide "voodoo" debugging of core files. This creates a zombie | |
462 | process as a child of the debugger, and loads it up with the data, | |
463 | stack, and regs of the core file. This allows you to call functions | |
464 | in the executable, to manipulate the data in the core file. | |
465 | ||
466 | GDB reopens the source file on every line, as you "next" through it. | |
467 | ||
468 | Referencing the vtbl member of a struct doesn't work. It prints OK | |
469 | if you print the struct, but it gets 0 if you try to deref it. | |
470 | ||
471 | Persistent command history: A feature where you could save off a list | |
472 | of the commands you did, so you can edit it into something that will bring | |
473 | the target to the same place every time you source it. | |
474 | This would also be useful for automated fast watchpointing; if you go | |
475 | past the place where it watchpoints, you just start it over again and | |
476 | do it more carefully. | |
477 | ||
478 | Deal with the SunOS 4.0 and 4.1.1 ptrace bug that loses the registers if | |
479 | the stack is paged out. | |
480 | ||
481 | Finish the C++ exception handling stub routines. Lint points them out | |
482 | as unused statics functions. | |
483 | ||
484 | Perhaps "i source" should take an argument like that of "list". | |
485 | ||
486 | See if core-aout.c's fetch_core_registers can be used on more machines. | |
487 | E.g. MIPS (mips-xdep.c). | |
488 | ||
489 | unpack_double() does not handle IEEE float on the target unless the host | |
490 | is also IEEE. Death on a vax. | |
491 | ||
492 | Set up interface between GDB and INFO so that you can hop into interactive | |
493 | INFO and back out again. When running under Emacs, should use Emacs | |
494 | info, else fork the info program. Installation of GDB should install | |
495 | its texinfo files into the info tree automagically, including the readline | |
496 | texinfo files. | |
497 | ||
498 | "help address" ought to find the "help set print address" entry. | |
499 | ||
500 | Remove the VTBL internal guts from printouts of C++ structs, unless | |
501 | vtblprint is set. | |
502 | ||
503 | Remove "at 0xnnnn" from the "b foo" response, if `print address off' and if | |
504 | it matches the source line indicated. | |
505 | ||
506 | The prompt at end of screen should accept space as well as CR. | |
507 | ||
508 | Check STORE_RETURN_VALUE on all architectures. Check near it in tm-sparc.h | |
509 | for other bogosities. | |
510 | ||
511 | Check for storage leaks in GDB, I'm sure there are a lot! | |
512 | ||
513 | vtblprint of a vtbl should demangle the names it's printing. | |
514 | ||
515 | Backtrace should point out what the currently selected frame is, in | |
516 | its display, perhaps showing "@3 foo (bar, ...)" or ">3 foo (bar, | |
517 | ...)" rather than "#3 foo (bar, ...)". | |
518 | ||
519 | "i program" should work for core files, and display more info, like what | |
520 | actually caused it to die. | |
521 | ||
522 | "x/10i" should shorten the long name, if any, on subsequent lines. | |
523 | ||
524 | Check through the code for FIXME comments and fix them. dbxread.c, | |
525 | blockframe.c, and plenty more. (I count 634 as of 940621 - sts) | |
526 | ||
527 | "next" over a function that longjumps, never stops until next time you happen | |
528 | to get to that spot by accident. E.g. "n" over execute_command which has | |
529 | an error. | |
530 | ||
531 | "set zeroprint off", don't bother printing members of structs which | |
532 | are entirely zero. Useful for those big structs with few useful | |
533 | members. | |
534 | ||
535 | GDB does four ioctl's for every command, probably switching terminal modes | |
536 | to/from inferior or for readline or something. | |
537 | ||
538 | terminal_ours versus terminal_inferior: cache state. Switch should be a noop | |
539 | if the state is the same, too. | |
540 | ||
541 | ptype $i6 = void??! | |
542 | ||
543 | Clean up invalid_float handling so gdb doesn't coredump when it tries to | |
544 | access a NaN. While this might work on SPARC, other machines are not | |
545 | configured right. | |
546 | ||
547 | "b value_at ; commands ; continue ; end" stops EVERY OTHER TIME! | |
548 | Then once you enter a command, it does the command, runs two more | |
549 | times, and then stops again! Bizarre... (This behaviour has been | |
550 | modified, but it is not yet 100% predictable when e.g. the commands | |
551 | call functions in the child, and while there, the child is interrupted | |
552 | with a signal, or hits a breakpoint.) | |
553 | ||
554 | help completion, help history should work. | |
555 | ||
556 | Check that we can handle stack trace through varargs AND alloca in same | |
557 | function, on 29K. | |
558 | ||
559 | wait_for_inferior loops forever if wait() gives it an error. | |
560 | ||
561 | "i frame" shows wrong "arglist at" location, doesn't show where the args | |
562 | should be found, only their actual values. | |
563 | ||
564 | There should be a way for "set" commands to validate the new setting | |
565 | before it takes effect. | |
566 | ||
567 | A mess of floating point opcodes are missing from sparc-opcode.h. | |
568 | Also, a little program should test the table for bits that are | |
569 | overspecified or underspecified. E.g. if the must-be-ones bits | |
570 | and the must-be-zeroes bits leave some fields unexamined, and the format | |
571 | string leaves them unprinted, then point this out. If multiple | |
572 | non-alias patterns match, point this out too. Finally, there should | |
573 | be a sparc-optest.s file that tries each pattern out. This file | |
574 | should end up coming back the same (modulo transformation comments) | |
575 | if fed to "gas" then the .o is fed to gdb for disassembly. | |
576 | ||
577 | Eliminate all the core_file_command's in all the xdep files. | |
578 | Eliminate separate declarations of registers[] everywhere. | |
579 | ||
580 | "ena d" is ambiguous, why? "ena delete" seems to think it is a command! | |
581 | ||
582 | Perhaps move the tdep, xdep, and nat files, into the config | |
583 | subdirectories. If not, at least straighten out their names so that | |
584 | they all start with the machine name. | |
585 | ||
586 | inferior_status should include stop_print_frame. It won't need to be | |
587 | reset in wait_for_inferior after bpstat_stop_status call, then. | |
588 | ||
589 | i line VAR produces "Line number not known for symbol ``var''.". I | |
590 | thought we were stashing that info now! | |
591 | ||
592 | We should be able to write to random files at hex offsets like adb. | |
593 | ||
594 | Make "target xxx" command interruptible. | |
595 | ||
596 | Handle add_file with separate text, data, and bss addresses. Maybe | |
597 | handle separate addresses for each segment in the object file? | |
598 | ||
599 | Handle free_named_symtab to cope with multiply-loaded object files | |
600 | in a dynamic linking environment. Should remember the last copy loaded, | |
601 | but not get too snowed if it finds references to the older copy. | |
602 | ||
603 | Generalize and Standardize the RPC interface to a target program, | |
604 | improve it beyond the "ptrace" interface, and see if it can become a | |
605 | standard for remote debugging. (This is talking about the vxworks | |
606 | interface. Seems unlikely to me that there will be "a standard" for | |
607 | remote debugging anytime soon --kingdon, 8 Nov 1994). | |
608 | ||
609 | Remove all references to: | |
610 | text_offset | |
611 | data_offset | |
612 | text_data_start | |
613 | text_end | |
614 | exec_data_offset | |
615 | ... | |
616 | now that we have BFD. All remaining are in machine dependent files. | |
617 | ||
618 | When quitting with a running program, if a core file was previously | |
619 | examined, you get "Couldn't read float regs from core file"...if | |
620 | indeed it can't. generic_mourn_inferior... | |
621 | ||
622 | Have remote targets give a warning on a signal argument to | |
623 | target_resume. Or better yet, extend the protocols so that it works | |
624 | like it does on the Unix-like systems. | |
625 | ||
626 | Sort help and info output. | |
627 | ||
628 | Re-organize help categories into things that tend to fit on a screen | |
629 | and hang together. | |
630 | ||
631 | renote-nindy.c handles interrupts poorly; it error()s out of badly | |
632 | chosen places, e.g. leaving current_frame zero, which causes core dumps | |
633 | on the next command. | |
634 | ||
635 | Add in commands like ADB's for searching for patterns, etc. We should | |
636 | be able to examine and patch raw unsymboled binaries as well in gdb as | |
637 | we can in adb. (E.g. increase the timeout in /bin/login without source). | |
638 | ||
639 | Those xdep files that call register_addr without defining it are | |
640 | probably simply broken. When reconfiguring this part of gdb, I could | |
641 | only make guesses about how to redo some of those files, and I | |
642 | probably guessed wrong, or left them "for later" when I have a | |
643 | machine that can attempt to build them. | |
644 | ||
645 | When doing "step" or "next", if a few lines of source are skipped between | |
646 | the previous line and the current one, print those lines, not just the | |
647 | last line of a multiline statement. | |
648 | ||
649 | When searching for C++ superclasses in value_cast in valops.c, we must | |
650 | not search the "fields", only the "superclasses". There might be a | |
651 | struct with a field name that matches the superclass name. This can | |
652 | happen when the struct was defined before the superclass (before the | |
653 | name became a typedef). | |
654 | ||
655 | Handling of "&" address-of operator needs some serious overhaul | |
656 | for ANSI C and consistency on arrays and functions. | |
657 | For "float point[15];": | |
658 | ptype &point[4] ==> Attempt to take address of non-lvalue. | |
659 | For "char *malloc();": | |
660 | ptype malloc ==> "char *()"; should be same as | |
661 | ptype &malloc ==> "char *(*)()" | |
662 | call printf ("%x\n", malloc) ==> weird value, should be same as | |
663 | call printf ("%x\n", &malloc) ==> correct value | |
664 | ||
665 | Fix dbxread.c symbol reading in the presence of interrupts. It | |
666 | currently leaves a cleanup to blow away the entire symbol table when a | |
667 | QUIT occurs. (What's wrong with that? -kingdon, 28 Oct 1993). | |
668 | ||
669 | Mipsread.c reads include files depth-first, because the dependencies | |
670 | in the psymtabs are way too inclusive (it seems to me). Figure out what | |
671 | really depends on what, to avoid recursing 20 or 30 times while reading | |
672 | real symtabs. | |
673 | ||
674 | value_add() should be subtracting the lower bound of arrays, if known, | |
675 | and possibly checking against the upper bound for error reporting. | |
676 | ||
677 | mipsread.c symbol table allocation and deallocation should be checked. | |
678 | My suspicion is that it's full of memory leaks. | |
679 | ||
680 | SunOS should have a target_lookup_symbol() for common'd things allocated | |
681 | by the shared library linker ld.so. | |
682 | ||
683 | When listing source lines, check for a preceding \n, to verify that | |
684 | the file hasn't changed out from under us. | |
685 | ||
686 | When listing source lines, eat leading whitespace corresponding to the | |
687 | line-number prefix we print. This avoids long lines wrapping. | |
688 | ||
689 | mipsread.c needs to check for old symtabs and psymtabs for the same | |
690 | files, the way it happens for dbxread.c and coffread.c, for VxWorks | |
691 | incremental symbol table reloading. | |
692 | ||
693 | Get all the remote systems (where the protocol allows it) to be able to | |
694 | stop the remote system when the GDB user types ^C (like remote.c | |
695 | does). For ebmon, use ^Ak. | |
696 | ||
697 | Possible feature: A version of the "disassemble" command which shows | |
698 | both source and assembly code ("set symbol-filename on" is a partial | |
699 | solution). | |
700 | ||
701 | investigate "x/s 0" (right now stops early) (I think maybe GDB is | |
702 | using a 0 address for bad purposes internally). | |
703 | ||
704 | Make "info path" and path_command work again (but independent of the | |
705 | environment either of gdb or that we'll pass to the inferior). | |
706 | ||
707 | Make GDB understand the GCC feature for putting octal constants in | |
708 | enums. Make it so overflow on an enum constant does not error_type | |
709 | the whole type. Allow arbitrarily large enums with type attributes. | |
710 | Put all this stuff in the testsuite. | |
711 | ||
712 | Make TYPE_CODE_ERROR with a non-zero TYPE_LENGTH more useful (print | |
713 | the value in hex; process type attributes). Add this to the | |
714 | testsuite. This way future compilers can add new types and old | |
715 | versions of GDB can do something halfway reasonable. | |
716 | ||
717 | Clean up formatting of "info registers" on MIPS and 88k. See if it | |
718 | is possible to do this generically across all target architectures. | |
719 | ||
720 | GDB gets bfd/corefile.c and gdb/corefile.c confused (this should be easy to | |
721 | repeat even with something more recent than GDB 4.9). | |
722 | ||
723 | Check that unmatched RBRAC doesn't abort(). | |
724 | ||
725 | Fix mdebugread.c:parse_type to do fundamental types right (see | |
726 | rs6000_builtin_type in stabsread.c for what "right" is--the point is | |
727 | that the debug format fixes the sizes of these things and it shouldn't | |
728 | depend on stuff like TARGET_PTR_BIT and so on. For mdebug, there seem | |
729 | to be separate bt* codes for 64 bit and 32 bit things, and GDB should | |
730 | be aware of that). Also use a switch statement for clarity and speed. | |
731 | ||
732 | Investigate adding symbols in target_load--some targets do, some | |
733 | don't. | |
734 | ||
735 | Put dirname in psymtabs and change lookup*symtab to use dirname (so | |
736 | /foo/bar.c works whether compiled by cc /foo/bar.c, or cd /foo; cc | |
737 | bar.c). | |
738 | ||
739 | Merge xcoffread.c and coffread.c. Use breakpoint_re_set instead of | |
740 | fixup_breakpoints. | |
741 | ||
742 | Fix byte order and int size sins in tm-a29k.h | |
743 | (EXTRACT_RETURN_VALUE). Perhaps should reproduce bug and verify fix | |
744 | (or perhaps should just fix it...). | |
745 | ||
746 | Make a watchpoint on a constant expression an error (or warning | |
747 | perhaps) | |
748 | ||
749 | Make a watchpoint which contains a function call an error (it is | |
750 | broken now, making it work is probably not worth the effort). | |
751 | ||
752 | Re-do calls to signal() in remote.c, and inflow.c (set_sigint_trap and | |
753 | so on) to be independent of the debugging target, using target_stop to | |
754 | stop the inferior. Probably the part which is now handled by | |
755 | interrupt_query in remote.c can be done without any new features in | |
756 | the debugging target. | |
757 | ||
758 | New test case based on weird.exp but in which type numbers are not | |
759 | renumbered (thus multiply defining a type). This currently causes an | |
760 | infinite loop on "p v_comb". | |
761 | ||
762 | Nuke baseclass_addr. | |
763 | ||
764 | Nuke USG define. | |
765 | ||
766 | "source file more recent" loses on re-read | |
767 | ||
768 | Fix 386 floating point so that floating point registers are real | |
769 | registers (but code can deal at run-time if they are missing, like | |
770 | mips and 68k). This would clean up "info float" and related stuff. | |
771 | ||
772 | Look at Solaris bug in interrupt.exp. Can get out of syscall with | |
773 | PRSABORT (syscall will return EINTR) but merely doing that leads to a | |
774 | "can't read memory" error. | |
775 | ||
776 | gcc -g -c enummask.c then gdb enummask.o, then "p v". GDB complains | |
777 | about not being able to access memory location 0. | |
778 | ||
779 | -------------------- enummask.c | |
780 | enum mask | |
781 | { | |
782 | ANIMAL = 0, | |
783 | VEGETABLE = 1, | |
784 | MINERAL = 2, | |
785 | BASIC_CATEGORY = 3, | |
786 | ||
787 | WHITE = 0, | |
788 | BLUE = 4, | |
789 | GREEN = 8, | |
790 | BLACK = 0xc, | |
791 | COLOR = 0xc, | |
792 | ||
793 | ALIVE = 0x10, | |
794 | ||
795 | LARGE = 0x20 | |
796 | } v; | |
797 | ||
798 | If try to modify value in file with "set write off" should give | |
799 | appropriate error not "cannot access memory at address 0x65e0". | |
800 | ||
801 | Why do we allow a target to omit standard register names (NO_STD_REGS | |
802 | in tm-z8k.h)? I thought the standard register names were supposed to | |
803 | be just that, standard. | |
804 | ||
c906108c SS |
805 | Allow core file without exec file on RS/6000. |
806 | ||
807 | Make sure "shell" with no arguments works right on DOS. | |
808 | ||
809 | Make gdb.ini (as well as .gdbinit) be checked on all platforms, so | |
810 | the same directory can be NFS-mounted on unix or DOS, and work the | |
811 | same way. | |
812 | ||
813 | cd ~/tmp/<M-?> causes infinite loop (where ~/tmp is a directory). | |
814 | ||
815 | Get SECT_OFF_TEXT stuff out of objfile_relocate (might be needed to | |
816 | get RS/6000 to work right, might not be immediately relevant). | |
817 | ||
818 | Clean up add_toc_to_loadinfo | |
819 | ||
820 | Think about attached processes and sharing terminal. | |
821 | ||
822 | John sez in reference to ignoring errors from tcsegpgrp if attach_flag: | |
823 | set_tty_state should not have any trouble with attached processes. | |
824 | Instead, the tty handling should leave the pgrp of the tty alone when | |
825 | attaching to processes (perhaps pass terminal_init_inferior a flag | |
826 | saying whether we're attaching). | |
827 | ||
828 | PAGE_SIZE redefined warnings on AIX. Probably should be using | |
829 | BFD_PAGE_SIZE throughout BFD. | |
830 | ||
831 | Rewrite proceed, wait_for_inferior, and normal_stop to clean them up. | |
832 | Suggestions: | |
833 | ||
834 | 1) Make each test in wait_for_inferior a seperate subroutine | |
835 | call. | |
836 | 2) Combine wait_for_inferior and normal_stop to clean up | |
837 | communication via global variables. | |
838 | 3) See if you can find some way to clean up the global | |
839 | variables that are used; possibly group them by data flow | |
840 | and information content? | |
841 | ||
842 | Work out some kind of way to allow running the inferior to be done as | |
843 | a sub-execution of, eg. breakpoint command lists. Currently running | |
844 | the inferior interupts any command list execution. This would require | |
845 | some rewriting of wait_for_inferior & friends, and hence should | |
846 | probably be done in concert with the above. | |
847 | ||
848 | Add function arguments to gdb user defined functions. | |
849 | ||
850 | Add convenience variables that refer to exec file, symbol file, | |
851 | selected frame source file, selected frame function, selected frame | |
852 | line number, etc. | |
853 | ||
854 | Add a "suspend" subcommand of the "continue" command to suspend gdb | |
855 | while continuing execution of the subprocess. Useful when you are | |
856 | debugging servers and you want to dodge out and initiate a connection | |
857 | to a server running under gdb. | |
858 | ||
859 | Add stab information to allow reasonable debugging of inline functions | |
860 | (possibly they should show up on a stack backtrace? With a note | |
861 | indicating that they weren't "real"?). | |
862 | ||
863 | Modify the naked "until" command to step until past the current source | |
864 | line, rather than past the current pc value. This is tricky simply | |
865 | because the low level routines have no way of specifying a multi-line | |
866 | step range, and there is no way of saying "don't print stuff when we | |
867 | stop" from above (otherwise could just call step many times). | |
868 | ||
869 | Modify the handling of symbols grouped through BINCL/EINCL stabs to | |
870 | allocate a partial symtab for each BINCL/EINCL grouping. This will | |
871 | seriously decrease the size of inter-psymtab dependencies and hence | |
872 | lessen the amount that needs to be read in when a new source file is | |
873 | accessed. | |
874 | ||
875 | Do an "x/i $pc" after each stepi or nexti. | |
876 | ||
877 | Modify all of the disassemblers to use printf_filtered to get correct | |
878 | more filtering. | |
879 | ||
880 | Modify gdb to work correctly with Pascal. | |
881 | ||
882 | Add a command for searching memory, a la adb. It specifies size, | |
883 | mask, value, start address. ADB searches until it finds it or hits | |
884 | an error (or is interrupted). | |
885 | ||
b83266a0 SS |
886 | Remove the range and type checking code and documentation, if not |
887 | going to implement. | |
888 | ||
c906108c SS |
889 | # Local Variables: |
890 | # mode: text | |
891 | # End: |