Clang crash compiling qt5

[Dimitry Andric]

On 10 Apr 2019, at 21:29, George Mitchell <george+freebsd at m5p.com> wrote:
> 
> On 2019-04-10 15:11, Dimitry Andric wrote:
>> On 10 Apr 2019, at 19:37, George Mitchell <george+freebsd at 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20190410/a8605b01/attachment.sig>