Created attachment 188103 [details] GDB backtrace when running /usr/lib64/libreoffice/programs/oosplash Fresh install of LibreOffice 7.5.3.2 on Gentoo. When built with clang and lto, launching the /usr/bin/libreoffice script or /usr/lib64/libreoffice/oosplash hangs indefinitely, whilst running /usr/lib64/libreoffice/soffice.bin works. I'm attaching a gdb backtrace. Other relevant elements: clang --version clang version 16.0.5 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/16/bin Configuration file: /etc/clang/clang.cfg /etc/clang/clang.cfg # This configuration file is used by clang driver. @gentoo-common.cfg /etc/clang/gentoo-common.cfg # This file contains flags common to clang, clang++ and clang-cpp. @gentoo-runtimes.cfg @gentoo-gcc-install.cfg @gentoo-hardened.cfg # bug #870001 -include "/usr/include/gentoo/maybe-stddefs.h" /etc/clang/cfg/gentoo-runtimes.cfg # This file is initially generated by sys-devel/clang-runtime. # It is used to control the default runtimes using by clang. --rtlib=libgcc --unwindlib=libgcc --stdlib=libstdc++ -fuse-ld=bfd /etc/clang/gentoo-gcc-install.cfg # This file is maintained by gcc-config. # It is used to specify the selected GCC installation. --gcc-install-dir="/usr/lib/gcc/x86_64-pc-linux-gnu/12" /etc/clang/gentoo-hardened.cfg # Some of these options are added unconditionally, regardless of # USE=hardened, for parity with sys-devel/gcc. -fstack-clash-protection -fstack-protector-strong -fPIE -include "/usr/include/gentoo/fortify.h" strace -p -f on the libreoffice process doesn't provide any output after process X attached. Relevant Gentoo bug https://bugs.gentoo.org/907905 (a little bit convoluted in the report, one has to admit). Let me know if I can give any additional information.
Additional note: the bug doesn't occur when building with gcc (with lto enabled) nor when building with clang, but without lto. So it seems to be somehow related to clang+lto
Stephan may be you have some tips here?
Dear guillaumedevolpiano, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug