Date: Wed, 10 Apr 2019 21:42:07 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: George Mitchell <george+freebsd@m5p.com> Cc: freebsd ports <freebsd-ports@freebsd.org> Subject: Re: Clang crash compiling qt5 Message-ID: <2B151D1E-DFF5-4C7B-8DE3-AAD49C704D23@FreeBSD.org> In-Reply-To: <123ee70c-d167-087a-d4be-d7f871f7fba6@m5p.com> References: <15210358-2ff9-54a2-d9c2-075ca4c0f335@m5p.com> <A6BAD9ED-68C0-4723-997C-8BF8F5E3C5C2@FreeBSD.org> <123ee70c-d167-087a-d4be-d7f871f7fba6@m5p.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_4EE530F9-390A-442B-92CD-A63AA5717708 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 10 Apr 2019, at 21:29, George Mitchell <george+freebsd@m5p.com> wrote: > > On 2019-04-10 15:11, Dimitry Andric wrote: >> On 10 Apr 2019, at 19:37, George Mitchell <george+freebsd@m5p.com> wrote: >>> >>> 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 >> >> Hi George, >> >> 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? >> > > 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. Okay, can you create a PR and attach one .sh and .cpp file which belong together (they should have the same random suffix of hex digits)? It is likely that we can then reproduce it independently of your particular setup, and without having to build qt5 and all its dependencies. :) -Dimitry --Apple-Mail=_4EE530F9-390A-442B-92CD-A63AA5717708 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCXK5HDwAKCRCwXqMKLiCW o1jvAKDuKSQ3dPZbp1ioyYM3GD3+3uKPOQCffDZ+ZcQc7MwDKKvN8CLS6yMFlR0= =5iHY -----END PGP SIGNATURE----- --Apple-Mail=_4EE530F9-390A-442B-92CD-A63AA5717708--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2B151D1E-DFF5-4C7B-8DE3-AAD49C704D23>