Re: Clang crash compiling qt5
On 2019-04-10 15:42, Dimitry Andric wrote: > On 10 Apr 2019, at 21:29, George Mitchell wrote: >> >> On 2019-04-10 15:11, Dimitry Andric wrote: >>>[...] >>> 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 > Thanks for your help! https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237185 -- George signature.asc Description: OpenPGP digital signature
Re: Clang crash compiling qt5
On 10 Apr 2019, at 21:29, George Mitchell wrote: > > On 2019-04-10 15:11, Dimitry Andric wrote: >> On 10 Apr 2019, at 19:37, George Mitchell 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 signature.asc Description: Message signed with OpenPGP
Re: Clang crash compiling qt5
On 2019-04-10 15:11, Dimitry Andric wrote: > On 10 Apr 2019, at 19:37, George Mitchell 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. Explicitly running "make configure" yields this (plus another core dump): ===> qt5-qmake-5.12.2 depends on executable: gmake - found ===> qt5-qmake-5.12.2 depends on package: pkgconf>=1.3.0_1 - found ===> qt5-qmake-5.12.2 depends on file: /usr/local/bin/python3.6 - found ===> 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 = -' > /usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.12.2/.qmake.cache echo 'QMAKE_LIBDIR_FLAGS = -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 = /usr/local/lib' >> /usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.12.2/.qmake.cache echo 'QMAKE_DEFAULT_INCDIRS = /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. > > -Dimitry > 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 signature.asc Description: OpenPGP digital signature
Re: Clang crash compiling qt5
On 10 Apr 2019, at 19:37, George Mitchell 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? 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. -Dimitry signature.asc Description: Message signed with OpenPGP
Clang crash compiling qt5
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 signature.asc Description: OpenPGP digital signature
