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

* README: Mention special build instructions for DJGPP. 

* NEWS: Update with FP features on x87 platforms, and
	DJGPP-related changes.
This commit is contained in:
Eli Zaretskii 2000-04-12 16:51:27 +00:00
parent ae678129eb
commit c63ce87553
3 changed files with 56 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/ChangeLog
View File

@ -1,3 +1,9 @@
2000-04-12 Eli Zaretskii <eliz@is.elta.co.il>
* README: Mention special build instructions for DJGPP.
* NEWS: Update with FP features on x87 platforms, and
DJGPP-related changes.
2000-04-12 Eli Zaretskii <eliz@is.elta.co.il>
* top.c (gdb_completer_file_name_break_characters): New variable.

44
gdb/NEWS
View File

@ -3,6 +3,50 @@
*** Changes since GDB-4.18:
* Improved support for debugging FP programs on x86 targets
Unified and much-improved support for debugging floating-point
programs on all x86 targets. In particular, ``info float'' now
displays the FP registers in the same format on all x86 targets, with
greater level of detail.
* Improvements and bugfixes in hardware-assisted watchpoints
It is now possible to watch array elements, struct members, and
bitfields with hardware-assisted watchpoints. Data-read watchpoints
on x86 targets no longer erroneously trigger when the address is
written.
* Improvements in the native DJGPP version of GDB
The distribution now includes all the scripts and auxiliary files
necessary to build the native DJGPP version on MS-DOS/MS-Windows
machines ``out of the box''.
The DJGPP version can now debug programs that use signals. It is
possible to catch signals that happened in the debuggee, deliver
signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
would kill the program being debugged.) Programs that hook hardware
interrupts (keyboard, timer, etc.) can also be debugged.
It is now possible to debug DJGPP programs that redirect their
standard handles or switch them to raw (as opposed to cooked) mode, or
even close them. The command ``run < foo > bar'' works as expected,
and ``info terminal'' reports useful information about the debuggee's
terminal, including raw/cooked mode, redirection, etc.
The DJGPP version now uses termios functions for console I/O, which
enables debugging graphics programs. Interrupting GDB with Ctrl-C
also works.
DOS-style file names with drive letters are now fully supported by
GDB.
It is now possible to debug DJGPP programs that switch their working
directory. It is also possible to rerun the debuggee any number of
times without restarting GDB; thus, you can use the same setup,
breakpoints, etc. for many debugging sessions.
* New native configurations
ARM GNU/Linux arm*-*-linux*

6
gdb/README
View File

@ -41,6 +41,9 @@ To build GDB, you can just do:
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
(Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
different; see the file gdb/config/djgpp/README for details.)
This will configure and build all the libraries as well as GDB.
If `configure' can't determine your system type, specify one as its
argument, e.g., sun4 or decstation.
@ -174,6 +177,9 @@ directory. That directory contains:
`gdb-4.18/utils'
A grab bag of random utilities.
Note: the following instructions are for building GDB on Unix or
Unix-like systems. Instructions for building with DJGPP for
MS-DOS/MS-Windows are in the file gdb/config/djgpp/README.
The simplest way to configure and build GDB is to run `configure'
from the `gdb-VERSION-NUMBER' source directory, which in this example