Hi, Il 04/02/25 14:16, Volker Hilsheimer ha scritto:
Well, the tool itself is built just fine; it's binary identical to one built without Coverity. It's more likely that Coverity is doing something like tracing it during the build process and something goes wrong there, so host tools aren't going to make a difference I'm afraid :(Thanks for looking after this Peppe, looks like things are working again? At least I got a few reports from Coverity Scan in the last days.
Volker managed to nerd-snipe me yesterday, and I had a second look at why qsb would still crash when running under Coverity.
I still don't know the _why_, but at least I have a workaround. Now QtQuick, QtMultimedia, QtLottie, and many more things that depended on qsb are now being built, so expect a massive surge of "newly found issues"...
Thanks,¹ The nitty gritty details after investigating, Coverity seems to overwrite execve(2) and inject itself via LD_PRELOAD into all the processes spawned during a build. How come this works for moc, uic, etc. but not for qsb? I have no idea. I've even replaced qsb with a dummy binary that just touches the outputs -- still crashes. The "solution" was to rename qsb, and add in its place a little C executable, statically linked, that cleans up LD_PRELOAD and issues a syscall(SYS_execve) calling the real binary. I have NO idea why this works.
-- Giuseppe D'Angelo | [email protected] | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - Trusted Software Excellence
smime.p7s
Description: Firma crittografica S/MIME
-- Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
