Date: Thu, 24 Oct 2002 10:41:58 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: current@FreeBSD.org, Alexander Kabaev <kan@FreeBSD.org>, Peter Wemm <peter@FreeBSD.org> Subject: Re: Groff problems (was Re: alpha tinderbox failure) Message-ID: <20021024074158.GA94686@sunbay.com> In-Reply-To: <15799.5316.331108.803590@grasshopper.cs.duke.edu> References: <200210210942.g9L9gLpM025724@beast.freebsd.org> <15796.17145.909288.498725@grasshopper.cs.duke.edu> <20021022142929.GB48398@sunbay.com> <20021022220221.3a8e2312.kabaev@bellatlantic.net> <15798.43826.90549.275914@grasshopper.cs.duke.edu> <20021023142044.GD31781@sunbay.com> <15798.56802.31765.434719@grasshopper.cs.duke.edu> <20021023180648.GA8656@sunbay.com> <15799.5316.331108.803590@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 23, 2002 at 05:29:40PM -0400, Andrew Gallatin wrote: >=20 >=20 >=20 > Ruslan Ermilov writes: > > OK, to summarize things. There was a single problem with two > > symptoms: 1) groff, if built dynamically, could not be run > > by ld-elf.so; 2) groff, if built statically, always failed > > with ``out of memory'', apparently due to the same bug. > >=20 > > Static hack is safe to delete because: > >=20 > > 1. groff that is built as part of the bootstrap-tools during > > buildworld will be built static anyway (see -DNOSHARED in > > BMAKE in Makefile.inc1) > >=20 > > 2. if you have a vulnerable kernel and rtld-elf, static > > linkage does not address the problem -- you get spurious > > ``out of memory'' even if you link groff statically. > >=20 > > If you agree, please feel free to commit the backout of > > the hack yourself -- I'm going to leave the computer now. :-) >=20 > Removed. =20 >=20 > Please review the following UPDATING entry: >=20 > --- UPDATING 3 Sep 2002 06:13:43 -0000 1.217 > +++ UPDATING 23 Oct 2002 21:24:44 -0000 > @@ -22,6 +22,19 @@ > integrity. Re-enabling write caching can substantially > improve > performance. >=20 > +20021023: > + Alphas with kernels from between 20020902 and 20021022 and/or > + rtld (ld-elf.so.1) older than 20021022 may experience problems > + with groff while doing a buildworld (kernel: "out of memory", > + rtld: "too few PT_LOAD segments"). > + > + So, to successfully upgrade your Alpha, you must either > + upgrade your kernel and rtld first (which might be a bit > + tricky), or avoid running the bootstrapped groff during the > + "transitional" buildworld. To avoid running groff during the > + transitional upgrade run make buildworld with -DNOMAN, > + -DNO_SHAREDOCS, and -DNO_LPR. > + > 20020831: > gcc has been upgraded to 3.2. It is not all binary compatible > with earlier versions of gcc for c++ programs. All c++ >=20 >=20 > Note: I have NOT tested this, beyond verifying that a kernel from Sep > 02 works fine. >=20 What commit is responsible for a breakage, this one? : peter 2002/09/03 14:18:17 PDT :=20 : Modified files: : sys/kern imgact_elf.c : Log: : Make the text segment locating heuristics from rev 1.121 more reliable : so that it works on the Alpha. This defines the segment that the entry : point exists in as 'text' and any others (usually one) as data. :=20 : Submitted by: tmm : Tested on: i386, alpha :=20 : Revision Changes Path : 1.125 +10 -15 src/sys/kern/imgact_elf.c Also I have verified (on beast) that previous version of Groff (1.17.1) does not have this problem -- groff has two PT_LOAD segments. Anyone cares to explain what's going on here? Why when I remove -fno-exceptions it creates two PT_LOAD segments, why it does not affect previous version of Groff? Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9t6RGUkv4P6juNwoRAm3DAJ9AOgrqXhT+2EnHl3jBvtRj16sYhwCeNPhr oBND5W5/7HwsvMEBvSNwCoQ= =V15g -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021024074158.GA94686>