2003-09-20  Andrew Cagney  <cagney@redhat.com>

	* NEWS: Mention the new backtrace mechanism, DWARF 2 CFI, hosted
	file I/O, multi-arch, TLS and NPTL, and Location Expressions.
	* PROBLEMS: Mention that mips*-*-*, powerpc*-*-*, sparc*-*-* and
	arm*-*-* do not use the new frame code.

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.120
diff -u -r1.120 NEWS
--- NEWS	11 Sep 2003 14:00:54 -0000	1.120
+++ NEWS	20 Sep 2003 20:55:43 -0000
@@ -16,11 +16,60 @@
 
 *** Changes in GDB 6.0:
 
+* New back-trace mechanism (includes DWARF 2 Call Frame Identification).
+
+DWARF 2's Call Frame Identification makes available compiler generated
+information that more exactly describes the program's run-time stack.
+By using this information, GDB is able to provide more robust stack
+back-traces.
+
+The i386, amd64 (nee, x86-64), Alpha, m68hc11, ia64, and m32r targets
+have been updated to use a new back-trace mechanism which includes
+DWARF 2 CFI support.
+
+* Hosted file I/O.
+
+GDB's remote protocol has been extended to include support for hosted
+file I/O (where the remote target uses GDB's file system).  See GDB's
+remote protocol documentation for details.
+
+* All targets using the new architecture framework.
+
+All of GDB's targets have been updated to use the new internal
+architecture framework.  The way is now open for future GDB releases
+to include cross-architecture native debugging support (i386 on amd64,
+ppc32 on ppc64).
+
+* GNU/Linux's Thread Local Storage (TLS)
+
+GDB now includes support for for the GNU/Linux implementation of
+per-thread variables.
+
+* GNU/Linux's Native POSIX Thread Library (NPTL)
+
+GDB's thread code has been updated to work with either the new
+GNU/Linux NPTL thread library or the older "LinuxThreads" library.
+
+* Separate debug info.
+
+GDB, in conjunction with BINUTILS, now supports a mechanism for
+automatically loading debug information from a separate file.  Instead
+of shipping full debug and non-debug versions of system libraries,
+system integrators can now instead ship just the stripped libraries
+and optional debug files.
+
 * GNU/Linux support for fork, vfork, and exec.
 
 The "catch fork", "catch exec", "catch vfork", and "set follow-fork-mode"
 commands are now implemented for GNU/Linux.  They require a 2.5.x or later
 kernel.
+
+* DWARF 2 Location Expressions
+
+DWARF 2 Location Expressions allow the compiler to more exactly
+describe the location of variables to the debugger.  By using this
+information, GDB is able to more robustly display the value of
+variables (even in optomized code).
 
 * GDB supports logging output to a file
 
Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.18
diff -u -r1.18 PROBLEMS
--- PROBLEMS	26 Aug 2003 03:08:32 -0000	1.18
+++ PROBLEMS	20 Sep 2003 20:55:43 -0000
@@ -3,6 +3,26 @@
 
 		See also: http://www.gnu.org/software/gdb/bugs/
 
+mips*-*-*
+powerpc*-*-*
+sparc*-*-*
+
+GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated
+to use the new frame mechanism.
+
+People encountering problems with these targets should consult GDB's
+web pages and mailing lists (http://www.gnu.org/software/gdb/) to see
+if there is an update.
+
+arm-*-*
+
+GDB's ARM target, in 6.0, has not been updated to use the new frame
+mechanism.
+
+Fortunatly the ARM target, in the GDB's mainline sources, has been
+updated so people encountering problems should consider downloading a
+more current GDB (http://www.gnu.org/software/gdb/current).
+
 gdb/1091: Constructor breakpoints ignored
 gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints