Change GDB over to GNU General Public License version 2.
[deliverable/binutils-gdb.git] / gdb / TODO
CommitLineData
dd3b648e
RP
1
2 gdb bug list
3 John Gilmore, gnu@cygnus.com
4
5This bug list is probably not up to date or accurate, but it reflects
6some known bugs in gdb, if you are into bug-hunting.
7
8
9Update the TODO list with all the lists of gdb bugs lying around on paper.
10
11"share" command should not need to be manually run. It should be run
12as soon as possible, automatically, both on "run" and on core files.
13
14It should be possible to use symbols from shared libraries before we know
15exactly where the libraries will be loaded. E.g. "b perror" before running
16the program. This could maybe be done as an extension of the "breakpoint
17re-evaluation" after new symbols are loaded.
18
19Make single_step() insert and remove breakpoints in one operation.
20
21Speed up single stepping by avoiding extraneous ptrace calls.
22
23Speed up single stepping by not inserting and removing breakpoints
24each time the inferior starts and stops.
25
26Speed up watchpoints by not single-stepping them, but do something
27faster like single-line execution.
28
29Update gdb.texinfo to include doc on the directory structure and
30the various tricks of building gdb.
31
32Do a tutorial in gdb.texinfo on how to do simple things in gdb.
33E.g. how to set a breakpoint that just prints something and continues.
34How to break on aborts. Etc.
35
36Do a "new features" section for release 4.
37
38Provide "voodoo" debugging of core files. This creates a zombie
39process as a child of the debugger, and loads it up with the data,
40stack, and regs of the core file. This allows you to call functions
41in the executable, to manipulate the data in the core file.
42
43GDB reopens the source file on every line, as you "next" through it.
44
45Referencing the vtbl member of a struct doesn't work. It prints OK
46if you print the struct, but it gets 0 if you try to deref it.
47
48Persistent command history: A feature where you could save off a list
49of the commands you did, so you can edit it into something that will bring
50the target to the same place every time you source it. Sun wants it.
51This would also be useful for automated fast watchpointing; if you go
52past the place where it watchpoints, you just start it over again and
53do it more carefully.
54
55Deal with the Sun ptrace bug that loses the registers if the stack is
56paged out.
57
58Finish the C++ exception handling stub routines. Lint points them out
59as unused statics functions.
60
61"i source" only shows you info about files that it can read. When it
62can't read a file and complains, you can't see any info about it, like
63where it was compiled. Perhaps "i source" should take an argument
64like that of "list".
65
66See if coredep.c's fetch_core_registers can be used on more machines.
67E.g. MIPS (mips-xdep.c).
68
69coredep.c is completely broken. Needs work just to compile, it uses
70"u" and doesn't declare it, etc.
71
72unpack_double() does not handle IEEE float on the target unless the host
73is also IEEE. Death on a vax.
74
75Test cross-debugging Unix-to-Unix.
76
77Check the RAPP remote protocol. What is it? It's in Makefile.dist
78and one ChangeLog entry.
79
80Set up interface between GDB and INFO so that you can hop into interactive
81INFO and back out again. When running under Emacs, should use Emacs
82info, else fork the info program. Installation of GDB should install
83its texinfo files into the info tree automagically, including the readline
84texinfo files..
85
86Improve backtrace output to avoid line wraps. Prettify it.
87
88"help address" ought to find the "help set addressprint" entry.
89
90Remove the VTBL internal guts from printouts of C++ structs, unless
91vtblprint is set.
92
93Remove "at 0xnnnn" from the "b foo" response, if !addressprint and if
94it matches the source line indicated.
95
96The prompt at end of screen should accept space as well as CR.
97
98"List" should put you into a pseudo-"more" where you can hit space
99to get more, forever to eof.
100
101Check STORE_RETURN_VALUE on all architectures. Check near it in tm-sparc.h
102for other bogosities.
103
104Check for storage leaks in GDB, I'm sure there are a lot!
105
106vtblprint of a vtbl should demangle the names it's printing.
107
108Backtrace should point out what the currently selected frame is, in its
109display, perhaps showing ">3 foo (bar, ...)" rather than "#3 foo (bar, ...)".
110
111"i program" should work for core files, and display more info, like what
112actually caused it to die.
113
114Hitting ^Z to an inferior doesn't work right, it takes several continues
115to make it actually go.
116
117"i fun" doesn't show misc function vector symbols.
118
119"x/10i" should shorten the long name, if any, on subsequent lines.
120
121Check through the code for FIXME comments and fix them. dbxread.c,
122blockframe.c, and plenty more.
123
124"next" over a function that longjumps, never stops until next time you happen
125to get to that spot by accident. E.g. "n" over execute_command which has
126an error.
127
128Watchpoints seem not entirely reliable.
129
130"set zeroprint off", don't bother printing members of structs which are entirely
131zero. Useful for those big structs with few useful members.
132
133GDB does four ioctl's for every command, probably switching terminal modes
134to/from inferior or for readline or something.
135
136terminal_ours versus terminal_inferior: cache state. Switch should be a noop
137if the state is the same, too.
138
139ptype $i6 = void??!
140
141Clean up invalid_float handling so gdb doesn't coredump when it tries to
142access a NaN. While this might work on SPARC, other machines are not
143configured right.
144
145"b value_at ; commands ; continue ; end" stops EVERY OTHER TIME!
146Then once you enter a command, it does the command, runs two more
147times, and then stops again! Bizarre... (This behaviour has been
148modified, but it is not yet 100% predictable when e.g. the commands
149call functions in the child, and while there, the child is interrupted
150with a signal, or hits a breakpoint.)
151
152Symbol completion with TAB does not unmangle names!
153
154help completion, help history should work.
155
156Symbol completion doesn't handle e.g. W::f. (symtab.c,
157make_symbol_completion_list).
158
159AMD version: ^C should do ^Ak to stop ebmon.
160
161Check that we can handle stack trace through varargs AND alloca in same
162function, on 29K.
163
164wait_for_inferior loops forever if wait() gives it an error.
165
166"i frame" arg formatting sucks. Should wrap lines.
167"bt" arg formatting needs the same treatment .
168
169"i frame" shows wrong "arglist at" location, doesn't show where the args
170should be found, only their actual values.
171
172Symbolic display of addrs, (& disassembly prefixes), don't show static
173fns, e.g. enable_command in gdb.
174
175'ptype yylval' ==> "union YYSTYPE { ..... }". However, it is not a
176union YYSTYPE, but is simply a YYSTYPE, which is a typedef for an
177unnamed union.
178
179"show all" should work.
180
181There should be a way for "set" commands to validate the new setting
182before it takes effect.
183
184The "display" command should become the "always" command, e.g.
185 "always print XXX"
186 "always p/xxx XXX"
187 "always echo foo"
188 "always call XXX"
189 "always x/i $pc", etc.
190
191A mess of floating point opcodes are missing from sparc-opcode.h.
192Also, a little program should test the table for bits that are
193overspecified or underspecified. E.g. if the must-be-ones bits
194and the must-be-zeroes bits leave some fields unexamined, and the format
195string leaves them unprinted, then point this out. If multiple
196non-alias patterns match, point this out too. Finally, there should
197be a sparc-optest.s file that tries each pattern out. This file
198should end up coming back the same (modulo transformation comments)
199if fed to "gas" then the .o is fed to gdb for disassembly.
200
201Merge the xxx-opcode.h files with gas again...
202
203Eliminate all the core_file_command's in all the xdep files.
204Eliminate separate declarations of registers[] everywhere.
205
206"ena d" is ambiguous, why? "ena delete" seems to think it is a command!
207
208Line numbers are off in some spots. In proceed() at 1st "oneproc = 1",
209it seems to run that statement, but it doesn't actually.
210
211Perhaps the tdep and xdep files, and the tm and xm files, into a config
212subdirectory. If not, at least straighten out their names so that
213they all start with the machine name.
214
215inferior_status should include stop_print_frame. It won't need to be
216reset in wait_for_inferior after bpstat_stop_status call, then.
217
218i line VAR produces "Line number not known for symbol ``var''.". I
219thought we were stashing that info now!
220
221Make sure we can handle executables with no symbol info, e.g. /bin/csh.
222
223We should be able to write to executables that aren't running.
224
225We should be able to write to random files at hex offsets like adb.
226
227Tiemann: It is very painful to look at fp registers that hold
228double precision values. GDB is happy to show them to you as single
229precision, but you cannot look at them as doubles. Perhaps casting
230should be changed to make this work; or maybe a new "set" option that
231sets the default fp precision to single, double, or quad. This is not
232urgent, but would be nice to get into GDB 4.0.
233
234Make "target xxx" command interruptible.
235
236Handle add_file with separate text, data, and bss addresses. Maybe
237handle separate addresses for each segment in the object file?
238
239Handle free_named_symtab to cope with multiply-loaded object files
240in a dynamic linking environment. Should remember the last copy loaded,
241but not get too snowed if it finds references to the older copy.
242
243Implement have_memory, have_stack, have_registers, have_execution.
244Memory: core, exec, child, vxworks even without child.
245stack: core, child, vxworks with child
246registers: core, child, vxworks with child
247execution: child, vxworks with child.
248
249The original BFD core dump reading routine would itself coredump when fed
250a garbage file as a core file. Does the current one?
251
252Breakpoints should not be inserted and deleted all the time. Only the
253one(s) there should be removed when we have to step over one. Support
254breakpoints that don't have to be removed to step over them.
255
256Stop reading stop_registers!
257
258Generalize and Standardize the RPC interface to a target program,
259improve it beyond the "ptrace" interface, and see if it can become a standard
260for remote debugging. Is WRS interested in donating their target-end
261code?
262
263Remove all references to:
264 text_offset
265 data_offset
266 text_data_start
267 text_end
268 exec_data_offset
269 ...
270now that we have BFD. All remaining are in machine dependent files.
271
272When quitting with a running program, if a core file was previously
273examined, you get "Couldn't read float regs from core file"...if
274indeed it can't. generic_mourn_inferior...
275
276...
277
278Check signal argument to remote proceed's and error if set.
279
280Handle floating point registers in core files under BFD. Currently
281they are punted.
282
283Sort help and info output.
284
285Re-organize help categories into things that tend to fit on a screen
286and hang together.
287
288When trying to print source lines but you can't find the file,
289print the file name and line number, and leave it selected anyway
290so "i source" will show it.
291
292renote-nindy.c handles interrupts poorly; it error()s out of badly
293chosen places, e.g. leaving current_frame zero, which causes core dumps
294on the next command.
295
296Add in commands like ADB's for searching for patterns, etc. We should
297be able to examine and patch raw unsymboled binaries as well in gdb as
298we can in adb. (E.g. increase the timeout in /bin/login without source).
299
300Those xdep files that call register_addr without defining it are
301probably simply broken. When reconfiguring this part of gdb, I could
302only make guesses about how to redo some of those files, and I
303probably guessed wrong, or left them "for later" when I have a
304machine that can attempt to build them.
305
306Use the complain() mechanism for handling all the error() calls in dbxread.c,
307and in similar situations in coffread.c and mipsread.c.
308
309When doing "step" or "next", if a few lines of source are skipped between
310the previous line and the current one, print those lines, not just the
311last line of a multiline statement.
312
313When searching for C++ superclasses in value_cast in valops.c, we must
314not search the "fields", only the "superclasses". There might be a
315struct with a field name that matches the superclass name. This can
316happen when the struct was defined before the superclass (before the
317name became a typedef).
318
319For "float point[15];":
320ptype &point[4] ==> Attempt to take address of non-lvalue.
321p &point[4] ==> Dereferences point[4] rather than giving you point+4.
322
323Fix symbol reading in the presence of interrupts. It currently leaves a
324cleanup to blow away the entire symbol table when a QUIT occurs.
325
This page took 0.037611 seconds and 4 git commands to generate.