This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[maint] Drop h8500 from build list


Hello,

As mentioned when posting that gdb_mbuild.sh rewrite, I noticed that the h8500 had problems. Namely, it couldn't manage:

(gdb) maint print architecture
gdbarch_dump: GDB_MULTI_ARCH = 0

gdbarch_dump: CALL_DUMMY_START_OFFSET # (internal_error ("/home/scratch/GDB/src/
gdb/gdbarch.c", 1012, "CALL_DUMMY_START_OFFSET"), 0)
/home/scratch/GDB/src/gdb/gdbarch.c:1015: internal-error: CALL_DUMMY_START_OFFSE
T
A problem internal to GDB has been detected. Further
debugging may prove unreliable.

So, it turns out that the internal error was added some time in 1999 and no one has, since, noticed. Pretty sure sign that the target is pretty dead^D^D^D^Dbroken.

committed,
Andrew
2002-11-25  Andrew Cagney  <ac131313@redhat.com>

	* MAINTAINERS: Mark h8500 as broken.  Breakage occured Fri Nov 5
	16:32:04 1999 Andrew Cagney <cagney@b1.cygnus.com>.

Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/gdb/MAINTAINERS,v
retrieving revision 1.210
diff -u -r1.210 MAINTAINERS
--- MAINTAINERS	7 Nov 2002 23:28:53 -0000	1.210
+++ MAINTAINERS	25 Nov 2002 20:56:13 -0000
@@ -84,7 +84,7 @@
 	h8300		--target=h8300hms ,-Werror
 			Maintenance only
 
-	h8500		--target=h8500hms -Werror
+	h8500		(--target=h8500hms broken)
 			Maintenance only
 			Not multi-arch, work in progress
 

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]