Date: Wed, 10 Apr 2019 15:29:13 -0400 From: George Mitchell <george+freebsd@m5p.com> To: Dimitry Andric <dim@FreeBSD.org> Cc: freebsd ports <freebsd-ports@freebsd.org> Subject: Re: Clang crash compiling qt5 Message-ID: <123ee70c-d167-087a-d4be-d7f871f7fba6@m5p.com> In-Reply-To: <A6BAD9ED-68C0-4723-997C-8BF8F5E3C5C2@FreeBSD.org> References: <15210358-2ff9-54a2-d9c2-075ca4c0f335@m5p.com> <A6BAD9ED-68C0-4723-997C-8BF8F5E3C5C2@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --V7A7CwTefsmwfcComJam59A8SrEWRhz7j Content-Type: multipart/mixed; boundary="oFDMG6eALQyytq4qT3mLLDemfqbSK0VYb"; protected-headers="v1" From: George Mitchell <george+freebsd@m5p.com> To: Dimitry Andric <dim@FreeBSD.org> Cc: freebsd ports <freebsd-ports@freebsd.org> Message-ID: <123ee70c-d167-087a-d4be-d7f871f7fba6@m5p.com> Subject: Re: Clang crash compiling qt5 References: <15210358-2ff9-54a2-d9c2-075ca4c0f335@m5p.com> <A6BAD9ED-68C0-4723-997C-8BF8F5E3C5C2@FreeBSD.org> In-Reply-To: <A6BAD9ED-68C0-4723-997C-8BF8F5E3C5C2@FreeBSD.org> --oFDMG6eALQyytq4qT3mLLDemfqbSK0VYb Content-Type: multipart/mixed; boundary="------------36FC99764E28A04B7F719E30" Content-Language: en-US This is a multi-part message in MIME format. --------------36FC99764E28A04B7F719E30 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2019-04-10 15:11, Dimitry Andric wrote: > On 10 Apr 2019, at 19:37, George Mitchell <george+freebsd@m5p.com> wrot= e: >> >> Yesterday I went through a round of updating and compiling ports. By >> all outward appearances it was successful. But this morning's daily >> status report revealed that clang had crashed on a signal 11 once >> while compiling each qt5 package. (For once, it was useful to have >> the "such-and-such installed" messages in the system log.) So I just >> tried recompiling qt5-qmake just now under "script". Sure enough, >> there was a clang crash about 15 seconds before the end of typescript,= >> though the typescript output looks completely innocuous as far as I >> can see, and all the qt5 packages and their dependencies seem to be >> functional at this point. Any idea about what's going on? >> >> The typescript output is at https://m5p.com/~george/typescript if >> you think it would be helpful. -- George >=20 > Hi George, >=20 > I don't see any crash report(s) in the typescript? Did clang drop two > files (a .sh and preprocessed .c or .cpp file) in /tmp, by any chance? >=20 Yes, it did -- quite a few of them. The 13 .cpp files are all identical. The .sh files are very similar but not identical. I attached one. Running it indeed causes another core dump. It sort of looks like it happened during a configuration step. Explicitly running "make configure" yields this (plus another core dump): =3D=3D=3D> qt5-qmake-5.12.2 depends on executable: gmake - found =3D=3D=3D> qt5-qmake-5.12.2 depends on package: pkgconf>=3D1.3.0_1 - fo= und =3D=3D=3D> qt5-qmake-5.12.2 depends on file: /usr/local/bin/python3.6 -= found =3D=3D=3D> Configuring for qt5-qmake-5.12.2 /bin/mkdir -p /usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.12.= 2 echo 'CMAKE_MODULE_TESTS =3D -' > /usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.12.2/.qmake.cache= echo 'QMAKE_LIBDIR_FLAGS =3D -L/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.12.2/lib' >> /usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.12.2/.qmake.cache= echo 'QMAKE_DEFAULT_LIBDIRS =3D /usr/local/lib' >> /usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.12.2/.qmake.cache= echo 'QMAKE_DEFAULT_INCDIRS =3D /usr/local/include' >> /usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.12.2/.qmake.cache= Creating qmake... > If you are using a stable branch, clang will not have been built with > assertions, and that can lead to crashes in some cases. You could try > commenting out the -DNDEBUG line in lib/clang/llvm.build.mk, and then > rebuilding and reinstalling world. Then try the port again. >=20 > -Dimitry >=20 Gosh, I cravenly confess to a lack of enthusiasm for doing this. My self-serving excuse is that no packages outside qt5 exhibited this problem, and even qt5 superficially appears to be okay ... -- George --------------36FC99764E28A04B7F719E30-- --oFDMG6eALQyytq4qT3mLLDemfqbSK0VYb-- --V7A7CwTefsmwfcComJam59A8SrEWRhz7j Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlyuRAkACgkQwRES3m+p 4fnbGw/+IASFCg6iDKtkWC1UVvYtcdG1Ze4lkVjlob0v3XMArG5YaOR0wVfBqD0F LUv6dStry8UVO49f/KQRwl9a6bKZuJRLNVvcvRrLwy8UmIY4aoLYvkTNwM9EyZRP keS0dnVzlMb+vxgYJiNAW9XHYLm1Ta3vt+BKY6MNC0W5eSKfY+hlOIOqAki5ummf hDrKa2ZoW4XLBFvWZ5pfapUP/p8KTF8w6Z2QYrfjDEVXQiqmxw3EAfovvIKBI+iM c6FR7rAE728mhQ+D9IqUpnlCf25nf8MI9rB+igWDoCP3lnm4JKMoHrx1qZ1Fz7xW jYpkDYMVFLRs0XbdXDks8Q7/0RNCNy3EOvlfrX9NlvnJNK1yQ485GOf1+6iuaZ2k eDoVA8NB+AXlFh0xRIMoJDY1MvuPx31CLVpa+RyzDPIFk++7hPua2e9dCns6FDEv qsqd7oz5rICe/krccHvf6C9scL6XjguIk2yWHb0isvMPrJ034NNYzk1FTKS5FKQj uKG7Rbs4onRauXxUZXtKGk6JpIniguMSZtXcfKNhEmRPBg7eQLZg9nfJvhBDy/oE 7KlQcVxsfOFhCWUL7JdWv1+1CiYjNUSHIPSR7Mt4872l1EVlVjR1Wqtnb3F2IQ13 5lbjVj5/LCXsRRfEGH2kZliWgrIhUXSvPp4faBwTCcrqC2tGD0E= =47CY -----END PGP SIGNATURE----- --V7A7CwTefsmwfcComJam59A8SrEWRhz7j--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?123ee70c-d167-087a-d4be-d7f871f7fba6>