Date: Wed, 24 May 2017 06:01:43 -0700 From: David Wolfskill <david@catwhisker.org> To: Dimitry Andric <dim@FreeBSD.org>, Konstantin Belousov <kostikbel@gmail.com> Cc: current@freebsd.org Subject: Re: ino64? r318606 -> r318739 OK; r318739 -> r318781 fails SIGSEGV Message-ID: <20170524130143.GL1190@albert.catwhisker.org> In-Reply-To: <20170524121033.GL1622@kib.kiev.ua> <F75597F9-86DF-4CD5-B8B0-5169D2D96DD9@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--cLlE6j+44ygFdGhU Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 24, 2017 at 02:10:08PM +0200, Dimitry Andric wrote: > ... > > building special pic c library > > --- libc.so.7 --- > > cc: error: unable to execute command: Segmentation fault (core dumped) > > cc: error: linker command failed due to signal (use -v to see invocatio= n) > > *** [libc.so.7] Error code 254 >=20 > Looks like your linker is crashing. Can you figure out: > 1) The exact linker command being run > 2) The path to the linker executable that crashes > 3) Backtrace of the crash >=20 > -Dimitry >=20 On Wed, May 24, 2017 at 03:10:33PM +0300, Konstantin Belousov wrote: > ... >=20 > If you perform build of r318739 on r318739 (i.e. build of the same sources > as installed on your machine), does the SIGSEGV occur ? >=20 > Anyway, get the core file loaded into gdb and get the backtrace, at least. Sorry for the delay; I'm way out of practice with using a debugger... and I see that gdb isn't in head now. lldb tells me: (lldb) bt * thread #1, name =3D 'ld', stop reason =3D signal SIGSEGV * frame #0: 0x0000000000000000 (lldb)=20 which isn't entirely unexpected, I suppose, given the nature of SIGSEGV. On the build machine, I "cloned" slice 4 to slice 3, then rebooted it =66rom slice 3, "updated" /usr/src to r318739 and told it to go build itself (while I continued poking at my laptop). The build machine has not yet completed the ">>> stage 4.2: building libraries" step -- recall that I had performed a "make clean" before cloning... -- but it has got quite a bit beyond the previous point of failure (still building clang). I have copied the ld.core and libc.so.7.meta files from the build machine to <http://www.catwhisker.org/~david/FreeBSD/head/r318781/>; (and made gzipped copies, as well). As far as I can tell, the "ld" command was: freebeast(12.0-C)[10] ls -lT `which ld` -r-xr-xr-x 2 root wheel 1706336 May 23 05:29:59 2017 /usr/bin/ld This, from: FreeBSD freebeast.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #352 r3= 18739M/318739:1200031: Tue May 23 05:16:24 PDT 2017 root@freebeast.catw= hisker.org:/common/S4/obj/usr/src/sys/GENERIC amd64 Late note: ">>> stage 4.2: building libraries" has completed on the build machine (building r318739 while running r318739). I apologize for not getting all the information you (both) requested, but thought it best to provisde what I can (sooner). Peace, david --=20 David H. Wolfskill david@catwhisker.org "[T]he president=E2=80=99s improper efforts to influence an ongoing investi= gation" See http://www.catwhisker.org/~david/publickey.gpg for my public key. --cLlE6j+44ygFdGhU Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZJYQ2XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XlUYIAJC0cxEpaxR5E6RY29Q5vYhV 7FyzXsd0JBYTOqDPK9j+vqkLoMDWjLq2qCYs5hMzQ66mFi36KcB/O2Ct6VjMkLBi 2yRKHlOUw/Ran3Acv4eMcb0rnRB8NnQ51EoSoXkpZLdrBd6rxvVNKFErEqL5MJmi Asjk50Ibg8FJcMiJxT9vvbMcsM8E+99vDlirXD5PfSKcCTJeCzc9zPnMF2awDwyx i1JYgiCENc5+3n17oS+wXscUuUduJLoOomvgFeKYgagTTyaFLPkzxpE+f2fjkMpx th6Mj8X07EssTLgNh9mB8MFX526PZa0iuTY1tsaNcH03WxyLGcsbq35JPQjeMFo= =ZLns -----END PGP SIGNATURE----- --cLlE6j+44ygFdGhU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170524130143.GL1190>