Can you please try a no-change rebuild against the new llvm?
My wild guess is that something caused symbols to change, or some miscompilation.
what changed in the llvm-3.9 in the last few uploads was just fixing builds with new glibc, and reducing size of debug symbols, because the new gcc-7/binutils increased it a lot, making the build fail.
So, I can't debug it further because the toolchain changed too much, would be nice a no-change rebuild in a ppa, to spot some ABI changes in the underlying libraries.
1) gcc switch
2) binutils fixes
3) dwarf changes
4) size of debug symbols reduced
5) glibc fixes.
This is the list, and the reason because we can't easily test an older llvm.
(I can backport it to zesty and see if it happens there, probably it won't because of older toolchain)
Can you please try a no-change rebuild against the new llvm?
My wild guess is that something caused symbols to change, or some miscompilation.
what changed in the llvm-3.9 in the last few uploads was just fixing builds with new glibc, and reducing size of debug symbols, because the new gcc-7/binutils increased it a lot, making the build fail.
So, I can't debug it further because the toolchain changed too much, would be nice a no-change rebuild in a ppa, to spot some ABI changes in the underlying libraries.
1) gcc switch
2) binutils fixes
3) dwarf changes
4) size of debug symbols reduced
5) glibc fixes.
This is the list, and the reason because we can't easily test an older llvm.
(I can backport it to zesty and see if it happens there, probably it won't because of older toolchain)