From owner-freebsd-toolchain@FreeBSD.ORG Sun Mar 2 17:55:20 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 583AD9D6; Sun, 2 Mar 2014 17:55:20 +0000 (UTC) Received: from aslan.scsiguy.com (ns1.scsiguy.com [70.89.174.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2B5D51813; Sun, 2 Mar 2014 17:55:19 +0000 (UTC) Received: from [192.168.0.61] (jt-mbp.home.scsiguy.org [192.168.0.61]) (authenticated bits=0) by aslan.scsiguy.com (8.14.7/8.14.7) with ESMTP id s22HtIOw001145 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 2 Mar 2014 10:55:19 -0700 (MST) (envelope-from gibbs@freebsd.org) Content-Type: multipart/signed; boundary="Apple-Mail=_FAF32865-6971-46E2-AD7F-D314F4E35FDC"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: ctfconvert broken for C++ objects? From: "Justin T. Gibbs" In-Reply-To: Date: Sun, 2 Mar 2014 10:55:20 -0700 Message-Id: References: <216B816A-8ADA-438F-B834-8C386C5BC460@FreeBSD.org> <20140220172608.GA85526@freebsd.org> <81C07491-7E51-4CF0-B257-88ED998EE2A0@FreeBSD.org> To: Dimitry Andric X-Mailer: Apple Mail (2.1874) Cc: freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Mar 2014 17:55:20 -0000 --Apple-Mail=_FAF32865-6971-46E2-AD7F-D314F4E35FDC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Mar 2, 2014, at 6:16 AM, Dimitry Andric wrote: > On 21 Feb 2014, at 23:47, Justin T. Gibbs wrote: >> On Feb 20, 2014, at 10:26 AM, Roman Divacky = wrote: >>=20 >>> The dwarf backend for ctfconvert was completely reimplemented a few = weeks ago. >>> It's now based on elftoolchain libdwarf. >>>=20 >>> Test on current. >>=20 >> The failures I=92ve experienced occur when attempting to ctfconvert = the C++ code in the base (e.g. ATF or devd). You can replicate the = failures on head by applying the share/mk patch below (a version of my = previous patch rebased on head). >=20 > I've just tried your patch, building devd, and it seemed to have = worked > just fine (though I had to use DEBUG_FLAGS=3D-g, otherwise ctfconvert > would complain there was no type data to convert): My buildworld currently dies with the ATF library: --- lib/atf__L --- = =20 --- fs.So --- = =20 ctfconvert -L VERSION -g fs.So = =20 --- process.So --- = =20 ctfconvert -L VERSION -g process.So = =20 --- lib/libutil__L --- = =20 ctfconvert -L VERSION -g property.o = =20 --- lib/atf__L --- = =20 --- fs.So --- = =20 Segmentation fault = =20 *** [fs.So] Error code 139 Can you build all of world with my patch? > This was last changed by Brooks in r251689: "Be more agressive about > bootstrapping ctfmerge and ctfconvert so builds from existing releases > have a chance of working properly". The range check was modified = from: >=20 > ((${BOOTSTRAPPING} < 800038 && !(${BOOTSTRAPPING} >=3D 700112 && = ${BOOTSTRAPPING} < 799999)) >=20 > to: >=20 > ((${BOOTSTRAPPING} < 1000034 && !(${BOOTSTRAPPING} >=3D 901505 && = ${BOOTSTRAPPING} < 999999)) >=20 > but maybe the 9.x range check is now too narrow? Why don=92t we always bootstrap the ctf toolchain when WITH_CTF is = defined? How else would a user migrate from an old tree to a new which = enables newly supported features of ctf (e.g. its use on C++ programs) = that require the new tools? =97 Justin --Apple-Mail=_FAF32865-6971-46E2-AD7F-D314F4E35FDC Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJTE3CIAAoJED9n8CuvaSf4Xk8H/jk5m2fEkmmbFghQ3Sk/xDat FtQ9tosQ1siFLvxyJEBnJQ892vKsmi+pcUtPDlRY50G+I9n2k2kOjqwh9dtpNoT1 Ygfu5KR/uViHetLqLZREfh3wGIR9n+m9uKmH/GbmQ7XmaOJwm+xlp24Yd4brgY38 /ioLknu+qjFdgQPPVrWZlWrF+3/yPepKaVVqWGMhLGsggx+qDStgeQHIPhTg6zh9 wjfZd3k4K2FjbRAbF1sw3kIN1n0dQ86fl2cg4JEeWCxqKOF5qlgC2XRepyxV+89+ 4p9I/11XvgNG8EDlVc6cBKjpQ47df6HyKH4gdcjWP/EgHu9qPywDLTO8eAlHeDg= =tBY0 -----END PGP SIGNATURE----- --Apple-Mail=_FAF32865-6971-46E2-AD7F-D314F4E35FDC--