From owner-freebsd-qa Sun Mar 11 18:40:14 2001 Delivered-To: freebsd-qa@freebsd.org Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by hub.freebsd.org (Postfix) with ESMTP id 237DE37B718; Sun, 11 Mar 2001 18:40:07 -0800 (PST) (envelope-from ler@lerctr.org) Received: (from ler@localhost) by lerami.lerctr.org (8.11.3/8.11.3/20010112/$Revision: 1.13 $) id f2C2e1l09729; Sun, 11 Mar 2001 20:40:01 -0600 (CST) (envelope-from ler) Date: Sun, 11 Mar 2001 20:40:00 -0600 From: Larry Rosenman To: Kris Kennaway Cc: stable@FreeBSD.ORG, qa@FreeBSD.ORG Subject: Re: cputype=486 Message-ID: <20010311204000.A9671@lerami.lerctr.org> References: <20010311120241.A15202@lerami.lerctr.org> <20010311145945.C66872@mollari.cthul.hu> <20010311193126.A6166@lerami.lerctr.org> <20010311175148.A82406@mollari.cthul.hu> <20010311195843.A7539@lerami.lerctr.org> <20010311201658.A8487@lerami.lerctr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.3.16i In-Reply-To: <20010311201658.A8487@lerami.lerctr.org>; from ler@lerctr.org on Sun, Mar 11, 2001 at 08:16:58PM -0600 X-Mailer: Mutt http://www.mutt.org/ Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Larry Rosenman [010311 20:16]: > * Larry Rosenman [010311 20:00]: > > * Kris Kennaway [010311 19:52]: > > > On Sun, Mar 11, 2001 at 07:31:26PM -0600, Larry Rosenman wrote: > > > > * Kris Kennaway [010311 17:00]: > > > > > On Sun, Mar 11, 2001 at 12:02:41PM -0600, Larry Rosenman wrote: > > > > > > If I make buildworld with CPUTYPE=3Di486 (on my P-III), and the= n=20 > > > > > > make installworld on the 486 target, we get a signal 4 in > > > > > > the first install of code, in strip.=20 > > > > >=20 > > > > > Odd. That suggests that gcc is outputting code which can't run o= n the > > > > > i486 because it uses an illegal instruction. > > > > >=20 > > > > > #define SIGILL 4 /* illegal instr. (not reset when= caught) */ > > > > >=20 > > > > > Does anyone else have 486 build reports with CPUTYPE, positive or= negative? > > > > > > > > even without CPUTYPE I'm getting the same thing.=20 > > >=20 > > > Well, that says it's not CPUTYPE at fault..that's good. Can you run > > > strip outside of installworld? Perhaps it was already replaced with > > > e.g. a pentium-optimized version by something else. > > It works fine, as does the install from the /tmp/install.$$ directory. > >=20 > > SO, where to now?=20 >=20 > OK, the ****NEWLY BUILT**** strip does *NOT* work on the 486.... >=20 >=20 > Script started on Sun Mar 11 20:10:54 2001 > $ pwd=0D=0D > /usr/obj/usr/src/i386/usr/libexec/elf=0D > $ ls -l strui=08 =08=08 =08ip=0D=0D > -rwxr-xr-x 1 root wheel 430232 Mar 11 12:14 strip=0D > $ ./strip=0D=0D > Illegal instruction =0D > $ ^D=0D=0D >=20 > Script done on Sun Mar 11 20:11:09 2001 >=20 > So, it appears CURRENT sources don't make a valid i486 executable. >=20 > attached is the make buildworld output. Here is a quick gdb... Script started on Sun Mar 11 20:38:03 2001 fw# gdb -c strip.core /usr/obj/usr/src/i386/usr/bin/strip=0D=0D GNU gdb 4.18=0D Copyright 1998 Free Software Foundation, Inc.=0D GDB is free software, covered by the GNU General Public License, and you ar= e=0D welcome to change it and/or distribute copies of it under certain condition= s.=0D Type "show copying" to see the conditions.=0D There is absolutely no warranty for GDB. Type "show warranty" for details.= =0D This GDB was configured as "i386-unknown-freebsd"...=0D (no debugging symbols found)...=0D Core was generated by `strip'.=0D Program terminated with signal 4, Illegal instruction.=0D #0 0x804ef9b in __swhatbuf ()=0D (gdb) where=0D #0 0x804ef9b in __swhatbuf ()=0D #1 0x804eea2 in __smakebuf ()=0D #2 0x80497a3 in __srefill ()=0D #3 0x8049401 in fgets ()=0D #4 0x804862c in getobjformat ()=0D #5 0x80481f3 in main ()=0D #6 0x8048135 in _start ()=0D (gdb) fw# ^D=08=08exit=0D Script done on Sun Mar 11 20:38:49 2001 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message