OpenE2K/binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update for 3.98 release.

Browse Source
This commit is contained in:
John Gilmore 1991-07-31 19:08:36 +00:00
parent 40dc32e580
commit adf2bb5864
4 changed files with 38 additions and 88 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/ChangeLog
View File

@ -1,3 +1,9 @@
Wed Jul 31 12:06:29 1991 John Gilmore (gnu at cygint.cygnus.com)
* GDB-3.98 release.
* TODO, Projects, WHATS.NEW: Update for gdb-3.98.
Tue Jul 30 17:26:39 1991 John Gilmore (gnu at cygint.cygnus.com)
* configure.in: Remove xm.h and tm.h even if we aren't linking

7
gdb/Projects
View File

@ -85,13 +85,6 @@ symbols to be read in simply to read a source file.
Allow patching of executables, a la "adb -w".
Improve the target interface so that targets can be stacked; e.g. an
exec file and a core file (memory references that the core file can't
satisfy are directed to the exec file); those two plus a child process.
The child doesn't let any refs through, but when the child terminates,
you are back to debugging the core file -- you might even want to swap
back and forth between the two, or between two core files.
Add a command for searching memory, a la adb. It specifies size,
mask, value, start address. ADB searches until it finds it or hits
an error (or is interrupted).

58
gdb/TODO
View File

@ -23,11 +23,15 @@ Speed up single stepping by avoiding extraneous ptrace calls.
Speed up single stepping by not inserting and removing breakpoints
each time the inferior starts and stops.
Breakpoints should not be inserted and deleted all the time. Only the
one(s) there should be removed when we have to step over one. Support
breakpoints that don't have to be removed to step over them.
Speed up watchpoints by not single-stepping them, but do something
faster like single-line execution. Speed them up tremendously on
machines that have watchpoint registers.
Update gdb.texinfo to include doc on the directory structure and
Update gdb-int.texinfo to include doc on the directory structure and
the various tricks of building gdb.
Do a tutorial in gdb.texinfo on how to do simple things in gdb.
@ -46,21 +50,18 @@ if you print the struct, but it gets 0 if you try to deref it.
Persistent command history: A feature where you could save off a list
of the commands you did, so you can edit it into something that will bring
the target to the same place every time you source it. Sun wants it.
the target to the same place every time you source it.
This would also be useful for automated fast watchpointing; if you go
past the place where it watchpoints, you just start it over again and
do it more carefully.
Deal with the Sun ptrace bug that loses the registers if the stack is
paged out.
Deal with the SunOS 4.0 and 4.1.1 ptrace bug that loses the registers if
the stack is paged out.
Finish the C++ exception handling stub routines. Lint points them out
as unused statics functions.
"i source" only shows you info about files that it can read. When it
can't read a file and complains, you can't see any info about it, like
where it was compiled. Perhaps "i source" should take an argument
like that of "list".
Perhaps "i source" should take an argument like that of "list".
See if coredep.c's fetch_core_registers can be used on more machines.
E.g. MIPS (mips-xdep.c).
@ -73,18 +74,16 @@ is also IEEE. Death on a vax.
Test cross-debugging Unix-to-Unix.
Check the RAPP remote protocol. What is it? It's in Makefile.dist
Check the RAPP remote protocol. What is it? It's in Makefile.in
and one ChangeLog entry.
Set up interface between GDB and INFO so that you can hop into interactive
INFO and back out again. When running under Emacs, should use Emacs
info, else fork the info program. Installation of GDB should install
its texinfo files into the info tree automagically, including the readline
texinfo files..
texinfo files.
Improve backtrace output to avoid line wraps. Prettify it.
"help address" ought to find the "help set addressprint" entry.
"help address" ought to find the "help set print address" entry.
Remove the VTBL internal guts from printouts of C++ structs, unless
vtblprint is set.
@ -113,8 +112,6 @@ actually caused it to die.
Hitting ^Z to an inferior doesn't work right, it takes several continues
to make it actually go.
"i fun" doesn't show misc function vector symbols.
"x/10i" should shorten the long name, if any, on subsequent lines.
Check through the code for FIXME comments and fix them. dbxread.c,
@ -124,7 +121,7 @@ blockframe.c, and plenty more.
to get to that spot by accident. E.g. "n" over execute_command which has
an error.
Watchpoints seem not entirely reliable.
Watchpoints seem not entirely reliable, though they haven't failed me recently.
"set zeroprint off", don't bother printing members of structs which are entirely
zero. Useful for those big structs with few useful members.
@ -160,9 +157,6 @@ function, on 29K.
wait_for_inferior loops forever if wait() gives it an error.
"i frame" arg formatting sucks. Should wrap lines.
"bt" arg formatting needs the same treatment .
"i frame" shows wrong "arglist at" location, doesn't show where the args
should be found, only their actual values.
@ -173,8 +167,6 @@ fns, e.g. enable_command in gdb.
union YYSTYPE, but is simply a YYSTYPE, which is a typedef for an
unnamed union.
"show all" should work.
There should be a way for "set" commands to validate the new setting
before it takes effect.
@ -205,7 +197,7 @@ Eliminate separate declarations of registers[] everywhere.
Line numbers are off in some spots. In proceed() at 1st "oneproc = 1",
it seems to run that statement, but it doesn't actually.
Perhaps the tdep and xdep files, and the tm and xm files, into a config
Perhaps move the tdep and xdep files, and the tm and xm files, into a config
subdirectory. If not, at least straighten out their names so that
they all start with the machine name.
@ -221,13 +213,6 @@ We should be able to write to executables that aren't running.
We should be able to write to random files at hex offsets like adb.
Tiemann: It is very painful to look at fp registers that hold
double precision values. GDB is happy to show them to you as single
precision, but you cannot look at them as doubles. Perhaps casting
should be changed to make this work; or maybe a new "set" option that
sets the default fp precision to single, double, or quad. This is not
urgent, but would be nice to get into GDB 4.0.
Make "target xxx" command interruptible.
Handle add_file with separate text, data, and bss addresses. Maybe
@ -237,23 +222,12 @@ Handle free_named_symtab to cope with multiply-loaded object files
in a dynamic linking environment. Should remember the last copy loaded,
but not get too snowed if it finds references to the older copy.
Implement have_memory, have_stack, have_registers, have_execution.
Memory: core, exec, child, vxworks even without child.
stack: core, child, vxworks with child
registers: core, child, vxworks with child
execution: child, vxworks with child.
The original BFD core dump reading routine would itself coredump when fed
a garbage file as a core file. Does the current one?
Breakpoints should not be inserted and deleted all the time. Only the
one(s) there should be removed when we have to step over one. Support
breakpoints that don't have to be removed to step over them.
Generalize and Standardize the RPC interface to a target program,
improve it beyond the "ptrace" interface, and see if it can become a standard
for remote debugging. Is WRS interested in donating their target-end
code?
improve it beyond the "ptrace" interface, and see if it can become a
standard for remote debugging.
Remove all references to:
text_offset

55
gdb/WHATS.NEW
View File

@ -33,7 +33,8 @@ Gdb's prompt is new-gdb=>.
What follows are the NEW set commands. The command ``help set'' will
print a complete list of old and new set commands. ``help set FOO''
will give a longer description of the variable FOO.
will give a longer description of the variable FOO. ``show'' will show
all of the variable descriptions and their current settings.
confirm on/off: Enables warning questions for operations that are
hard to recover from, e.g. rerunning the program while
@ -66,15 +67,15 @@ radix N: Sets the default radix for input and output. It can be set
to 8, 10, or 16. Note that the argument to "radix" is interpreted
in the current radix, so "set radix 10" is always a no-op.
screen-height N: This integer value is the number of lines on a page. Default
is 24, the current `stty rows'' setting, or the ``li#''
setting from the termcap entry matching the environment
variable TERM.
height N: This integer value is the number of lines on a page. Default
is 24, the current `stty rows'' setting, or the ``li#''
setting from the termcap entry matching the environment
variable TERM.
screen-width N: This integer value is the number of characters on a line.
Default is 80, the current `stty cols'' setting, or the ``co#''
setting from the termcap entry matching the environment
variable TERM.
width N: This integer value is the number of characters on a line.
Default is 80, the current `stty cols'' setting, or the ``co#''
setting from the termcap entry matching the environment
variable TERM.
Note: ``set screensize'' is obsolete. Use ``set height'' and
``set width'' instead.
@ -175,39 +176,15 @@ frames without printing.
'dir' now adds directories to the FRONT of the source search path.
The path starts off empty. Source files that contain debug information
about the directory in which they were compiled can be found even
with an empty path; GCC includes this information. If GDB can't find
your source file in the current directory, type "dir .".
* Features removed in this release
``info types'' has been removed, since it printed builtin types in a
confusing fashion, and did not do useful things with typedefs. ``ptype''
or ``whatis'' are more useful commands for dealing with types..
with an empty path; Sun CC and GCC include this information. If GDB can't
find your source file in the current directory, type "dir .".
* Configuring GDB for compilation
For normal use, type ``config.gdb host''. Hosts now handled are:
3b1 altos altosgas arm bigmips convex hp300bsd hp300hpux i386v i386v-g
i386v32 i386v32-g isi littlemips m88k merlin news news1000 none np1 pn
pyramid sun2os3 sun2os4 sun386 sun3os3 sun3os4 sun4os3 sun4os4 symmetry
umax vax
Type config.gdb +host to get a full description of each host.
You can now build gdb conveniently for several architectures from the
same sources. If config.gdb is run from a subdirectory, it configures
the Makefile to use source files from '..'. Each subdirectory can be
indpendently configured. An explicit source file directory can also
be specified with the +srcdir=xxx option. Due to obscure search rules
in the C preprocessor, if you have previously built gdb in the main
directory, run 'make cleanconfig' in the top level directory before
building it in a subdirectory.
For normal use, type ``./configure host''. See README or gdb.texinfo
for more details.
GDB now handles cross debugging. If you are remotely debugging between
two different machines, type ``config.gdb host target''.
Host is the machine where gdb will run; target is the machine
two different machines, type ``./configure host -target=targ''.
Host is the machine where gdb will run; targ is the machine
where the program that you are debugging will run.
Type config.gdb +target to get a full description of each target.