Doc updates for 4.1.
This commit is contained in:
parent
0476df731c
commit
24db5b8775
1 changed files with 59 additions and 5 deletions
|
@ -1,5 +1,16 @@
|
|||
What has changed since GDB-3.5?
|
||||
(Organized release by release)
|
||||
|
||||
*** Changes in GDB-4.1:
|
||||
|
||||
* Multiple source language support
|
||||
|
||||
GDB now has internal scaffolding to handle several source languages.
|
||||
It determines the type of each source file from its filename extension,
|
||||
and will switch expression parsing and number formatting to match the
|
||||
language of the function in the currently selected stack frame.
|
||||
You can also specifically set the language to be used, with
|
||||
`set language c' or `set language modula-2'.
|
||||
|
||||
* GDB and Modula-2
|
||||
|
||||
|
@ -10,7 +21,54 @@ continue through the fall of 1991 and into 1992.
|
|||
|
||||
Other Modula-2 compilers are currently not supported, and attempting to
|
||||
debug programs compiled with them will likely result in an error as the
|
||||
symbol table of the executable is read in.
|
||||
symbol table is read. Feel free to work on it, though!
|
||||
|
||||
There are hooks in GDB for strict type checking and range checking,
|
||||
in the `Modula-2 philosophy', but they do not currently work.
|
||||
|
||||
* set write on/off
|
||||
|
||||
GDB can now write to executable and core files (e.g. patch
|
||||
a variable's value). You must turn this switch on, specify
|
||||
the file ("exec foo" or "core foo"), *then* modify it, e.g.
|
||||
by assigning a new value to a variable. Modifications take
|
||||
effect immediately.
|
||||
|
||||
* Automatic SunOS shared library reading
|
||||
|
||||
When you run your program, GDB automatically determines where its
|
||||
shared libraries (if any) have been loaded, and reads their symbols.
|
||||
The `share' command is no longer needed. This also works when
|
||||
examining core files.
|
||||
|
||||
* set listsize
|
||||
|
||||
You can specify the number of lines that the `list' command shows.
|
||||
The default is 10.
|
||||
|
||||
* New machines supported (host and target)
|
||||
|
||||
SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
|
||||
Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
|
||||
Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
|
||||
|
||||
* New hosts supported (not targets)
|
||||
|
||||
IBM RT/PC: romp-ibm-aix or rtpc
|
||||
|
||||
* New targets supported (not hosts)
|
||||
|
||||
AMD 29000 embedded with COFF a29k-none-coff
|
||||
AMD 29000 embedded with a.out a29k-none-aout
|
||||
Ultracomputer remote kernel debug a29k-nyu-kern
|
||||
|
||||
* New remote interfaces
|
||||
|
||||
AMD 29000 Adapt
|
||||
AMD 29000 Minimon
|
||||
|
||||
|
||||
*** Changes in GDB-4.0:
|
||||
|
||||
* New Facilities
|
||||
|
||||
|
@ -109,10 +167,6 @@ print asm-demangle on/off: Same, for assembler level printouts
|
|||
|
||||
print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
|
||||
|
||||
write on/off: GDB can now write to executable and core files (e.g. patch
|
||||
a variable's value) if you turn this switch on, specify
|
||||
the file ("exec foo" or "core foo"), then modify it, e.g.
|
||||
by assigning a new value to a variable.
|
||||
|
||||
* Support for Epoch Environment.
|
||||
|
||||
|
|
Loading…
Reference in a new issue