[patch/rfc/6.2] PROBLEMS and NEWS updates / end-of-life for the frame code

[Andrew Cagney <cagney@gnu.org>]

[-- Attachment #1: Type: text/plain, Size: 112 bytes --]

Hello,

This patch updates the PROBLEMS and NEWS files giving a more current 
status of the frame code.

Andrew

[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 2644 bytes --]

2004-07-21  Andrew Cagney  <cagney@gnu.org>

	* NEWS: END-OF-LIFE frame compatibility module.
	* PROBLEMS: For "Stack backtraces", remove powerpc, hppa and mips
	specific comments.

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.154.2.4
diff -p -u -r1.154.2.4 NEWS
--- NEWS	21 Jul 2004 16:16:56 -0000	1.154.2.4
+++ NEWS	21 Jul 2004 18:44:30 -0000
@@ -52,6 +52,29 @@ OpenBSD/powerpc					powerpc-*-openbsd*
 NetBSD/vax					vax-*-netbsd*
 OpenBSD/vax					vax-*-openbsd*
 
+* END-OF-LIFE frame compatibility module
+
+GDB's internal frame infrastructure has been completely rewritten.
+The new infrastructure making it possible to support key new features
+including DWARF 2 Call Frame Information.  To aid in the task of
+migrating old configurations to this new infrastructure, a
+compatibility module, that allowed old configurations to continue to
+work, was also included.
+
+GDB 6.2 will be the last release to include this frame compatibility
+module.  This change directly impacts the following configurations:
+
+h8300-*-*
+mcore-*-*
+mn10300-*-*
+ns32k-*-*
+sh64-*-*
+v850-*-*
+xstormy16-*-*
+
+Unless there is activity to revive these configurations, they will
+made OBSOLETE by GDB 6.3, and REMOVED from GDB 6.4.
+
 * REMOVED configurations and files
 
 Sun 3, running SunOS 3				m68*-*-sunos3*
Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.31.2.2
diff -p -u -r1.31.2.2 PROBLEMS
--- PROBLEMS	21 Jul 2004 16:16:56 -0000	1.31.2.2
+++ PROBLEMS	21 Jul 2004 18:44:30 -0000
@@ -121,24 +121,3 @@ gdb/1505: [regression] gdb prints a bad 
 When backtracing a thread, gdb does not stop when it reaches the
 outermost frame, instead continuing until it hits garbage.  This is
 sensitive to the operating system and thread library.
-
-hppa*-*-*
-mips*-*-*
-
-The MIPS and HPPA backtrace code has only very recently been updated
-to use GDB's new frame mechanism.  At present there are still a few
-problems, in particular backtraces through signal handlers do not
-work.
-
-People encountering problems with these architectures should consult
-GDB's web pages and mailing lists (http://www.gnu.org/software/gdb/)
-to see if there are updates.
-
-powerpc*-*-*
-
-PowerPC architecture support, in 6.1, does not use the new frame code.
-
-Fortunately, PowerPC architecture support, in GDB's mainline sources,
-have been updated.  People encountering problems should consider
-downloading a more current snapshot of GDB
-(http://www.gnu.org/software/gdb/current/).