This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: [RFA] Additions to NEWS and README
- To: Eli Zaretskii <eliz at is dot elta dot co dot il>
- Subject: Re: [RFA] Additions to NEWS and README
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Fri, 07 Apr 2000 11:48:59 +1000
- CC: gdb-patches at sourceware dot cygnus dot com, Chris Faylor <cgf at cygnus dot com>
- Organization: Cygnus Solutions
- References: <200004061218.IAA21989@mescaline.gnu.org>
The news changes are all fine with me - check-em in. Thanks!
For the README changes, I wonder if that comment should be expanded to
also warn people about the hazards of cygwin. Chris?
Andrew
Eli Zaretskii wrote:
>
> I'd like approval for the following additions to NEWS and README:
>
> --- gdb/README.~0 Mon Apr 26 20:44:00 1999
> +++ gdb/README Wed Apr 5 17:48:34 2000
> @@ -41,6 +41,9 @@
> 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 @@
> `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
> --- gdb/NEWS.~0 Thu Dec 23 00:05:42 1999
> +++ gdb/NEWS Wed Apr 5 18:23:12 2000
> @@ -9,6 +9,50 @@
> without first loading a symbol file, GDB will now attempt to locate and
> load symbols from the running process's executable file.
>
> +* 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*