From c63ce875537178489c14607623e0456e16bbcccc Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Wed, 12 Apr 2000 16:51:27 +0000 Subject: [PATCH] * README: Mention special build instructions for DJGPP. * NEWS: Update with FP features on x87 platforms, and DJGPP-related changes. --- gdb/ChangeLog | 6 ++++++ gdb/NEWS | 44 ++++++++++++++++++++++++++++++++++++++++++++ gdb/README | 6 ++++++ 3 files changed, 56 insertions(+) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index ed5d619..6f11eed 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,11 @@ 2000-04-12 Eli Zaretskii + * README: Mention special build instructions for DJGPP. + * NEWS: Update with FP features on x87 platforms, and + DJGPP-related changes. + +2000-04-12 Eli Zaretskii + * top.c (gdb_completer_file_name_break_characters): New variable. (line_completion_function): When completing on file names, use gdb_completer_file_name_break_characters as word break diff --git a/gdb/NEWS b/gdb/NEWS index aa7d338..8a7320f 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -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* diff --git a/gdb/README b/gdb/README index 46b9074..bb3e0e1 100644 --- a/gdb/README +++ b/gdb/README @@ -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 -- 2.7.4