From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc/6.2] PROBLEMS and NEWS updates / end-of-life for the frame code
Date: Mon, 26 Jul 2004 18:32:00 -0000 [thread overview]
Message-ID: <41054E45.5020108@gnu.org> (raw)
In-Reply-To: <40FEBACF.3060902@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 304 bytes --]
> Hello,
>
> This patch updates the PROBLEMS and NEWS files giving a more current status of the frame code.
I've committed the attached (mainline and 6.2 branch). This also goes
through the MAINTAINERS file marking all affected architectures as
"broken" (so that gdb_mbuild.sh skips them).
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 4558 bytes --]
2004-07-26 Andrew Cagney <cagney@gnu.org>
* MAINTAINERS: Mark the xstormy16, sh64, ns32k, mn10300, mcore,
and h8300 as broken.
* NEWS: END-OF-LIFE frame compatibility module.
* PROBLEMS: For "Stack backtraces", remove powerpc, hppa and mips
specific comments.
Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/gdb/MAINTAINERS,v
retrieving revision 1.281
diff -p -u -r1.281 MAINTAINERS
--- MAINTAINERS 14 Jun 2004 17:35:07 -0000 1.281
+++ MAINTAINERS 26 Jul 2004 18:27:45 -0000
@@ -82,7 +82,7 @@ maintainer works with the native maintai
frv --target=frv-elf ,-Werror
Maintenance only
- h8300 --target=h8300hms ,-Werror
+ h8300 --target=h8300hms broken
Maintenance only
h8500 Deleted.
@@ -107,7 +107,7 @@ maintainer works with the native maintai
m88k --target=m88k-openbsd ,-Werror
Mark Kettenis kettenis@gnu.org
- mcore --target=mcore-elf ,-Werror
+ mcore --target=mcore-elf broken
Maintenance only
mips --target=mips-elf ,-Werror
@@ -115,10 +115,10 @@ maintainer works with the native maintai
mn10200 Deleted.
- mn10300 --target=mn10300-elf ,-Werror
+ mn10300 --target=mn10300-elf broken
Maintenance only
- ns32k --target=ns32k-netbsd ,-Werror
+ ns32k --target=ns32k-netbsd broken
Maintenance only
pa --target=hppa-elf ,-Werror
@@ -131,6 +131,7 @@ maintainer works with the native maintai
(contact DJ Barrow djbarrow@de.ibm.com)
sh --target=sh-elf ,-Werror
+ --target=sh64-elf broken
Elena Zannoni ezannoni@redhat.com
sparc --target=sparc-elf ,-Werror
@@ -138,7 +139,7 @@ maintainer works with the native maintai
tic80 Deleted.
- v850 --target=v850-elf ,-Werror
+ v850 --target=v850-elf broken
Maintenance only
vax --target=vax-netbsd ,-Werror
@@ -149,7 +150,7 @@ maintainer works with the native maintai
x86-64 --target=x86_64-linux-gnu ,-Werror
Maintenance only
- xstormy16 --target=xstormy16-elf ,-Werror
+ xstormy16 --target=xstormy16-elf broken
Corinna Vinschen vinschen@redhat.com
z8k Deleted.
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 26 Jul 2004 18:27:46 -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 be
+made OBSOLETE in 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 26 Jul 2004 18:27:47 -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/).
prev parent reply other threads:[~2004-07-26 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 18:49 Andrew Cagney
2004-07-26 18:32 ` Andrew Cagney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41054E45.5020108@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox