Fix the date of the last entry.

[binutils.git] / gdb / NEWS

diff --git a/gdb/NEWS b/gdb/NEWS
index 080bfb2ca3345dffd84d389b0aacc12886887918..64cb12c6825d65d5fe7c549ef56f9670d8966ca8 100644 (file)
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -1,10 +1,60 @@
                What has changed in GDB?
             (Organized release by release)
 
                What has changed in GDB?
             (Organized release by release)
 

-*** Changes since GDB-4.18:
+*** Changes in GDB 5.0:
+
+* 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*
+PowerPC GNU/Linux                              powerpc-*-linux*

 
 * New targets
 
 
 * New targets
 

+Motorola MCore                                 mcore-*-*

 x86 VxWorks                                    i[3456]86-*-vxworks*
 PowerPC VxWorks                                        powerpc-*-vxworks*
 TI TMS320C80                                   tic80-*-*
 x86 VxWorks                                    i[3456]86-*-vxworks*
 PowerPC VxWorks                                        powerpc-*-vxworks*
 TI TMS320C80                                   tic80-*-*


@@ -14,6 +64,24 @@ TI TMS320C80                                 tic80-*-*
 Altos 3068                                     m68*-altos-*
 Convex                                         c1-*-*, c2-*-*
 Pyramid                                                pyramid-*-*
 Altos 3068                                     m68*-altos-*
 Convex                                         c1-*-*, c2-*-*
 Pyramid                                                pyramid-*-*

+ARM RISCix                                     arm-*-* (as host)
+Tahoe                                          tahoe-*-*
+
+Configurations that have been declared obsolete will be commented out,
+but the code will be left in place.  If there is no activity to revive
+these configurations before the next release of GDB, the sources will
+be permanently REMOVED.
+
+* New features for SVR4
+
+On SVR4 native platforms (such as Solaris), if you attach to a process
+without first loading a symbol file, GDB will now attempt to locate and
+load symbols from the running process's executable file.
+
+* Many C++ enhancements
+
+C++ support has been greatly improved. Overload resolution now works properly
+in almost all cases. RTTI support is on the way.

 
 * Remote targets can connect to a sub-program
 
 
 * Remote targets can connect to a sub-program
 


@@ -34,6 +102,34 @@ instead of 64 bits has been fixed.
 The command ``set remote-mips64-transfers-32bit-regs on'' has been
 added to provide backward compatibility with older versions of GDB.
 
 The command ``set remote-mips64-transfers-32bit-regs on'' has been
 added to provide backward compatibility with older versions of GDB.
 

+* ``set remotebinarydownload'' replaced by ``set remote X-packet''
+
+The command ``set remotebinarydownload'' command has been replaced by
+``set remote X-packet''.  Other commands in ``set remote'' family
+include ``set remote P-packet''.
+
+* Breakpoint commands accept ranges.
+
+The breakpoint commands ``enable'', ``disable'', and ``delete'' now
+accept a range of breakpoints, e.g. ``5-7''.  The tracepoint command
+``tracepoint passcount'' also accepts a range of tracepoints.
+
+* ``apropos'' command added.
+
+The ``apropos'' command searches through command names and
+documentation strings, printing out matches, making it much easier to
+try to find a command that does what you are looking for.
+
+* New MI interface
+
+A new machine oriented interface (MI) has been added to GDB.  This
+interface is designed for debug environments running GDB as a separate
+process.  This is part of the long term libGDB project.  See
+gdb/mi/gdbmi.texinfo for further information.  It can be enabled by
+configuring with:
+
+       .../configure --enable-gdbmi
+

 *** Changes in GDB-4.18:
 
 * New native configurations
 *** Changes in GDB-4.18:
 
 * New native configurations