https://bugs.kde.org/show_bug.cgi?id=411425
Bug ID: 411425
Summary: The link ordering is correct by chance only and init
of gdrive.so fails when linking with LTO enabled
Product: libkgapi
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: drive
Assignee: dvra...@kde.org
Reporter: h...@urpla.net
Target Milestone: ---
Created attachment 122413
--> https://bugs.kde.org/attachment.cgi?id=122413&action=edit
patch to provoke failure, even if LTO is disabled
SUMMARY
The linking is ordered alphabetically in src/drive/CMakeLists.txt, and fails
with a segfault, if LTO is used, because LTO doesn't stick to the supplied
linking order, if it sees a chance to optimize module locality.
See:
https://bugzilla.opensuse.org/show_bug.cgi?id=1148217
Specifically:
https://bugzilla.opensuse.org/show_bug.cgi?id=1148217#c19
and
https://bugzilla.opensuse.org/show_bug.cgi?id=1148217#c21
STEPS TO REPRODUCE
apply attached patch, compile, install, and run "kioclient5 exec gdrive:/"
OBSERVED RESULT
Failure: The process for the protocol gdrive failed unexpectedly. (translated)
EXPECTED RESULT
No failure
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Tumbleweed 20190824
(available in About System)
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.13.0
ADDITIONAL INFORMATION
Linking with LTO disabled fixed the problem, but the correct initialization
order should be addressed in some future version.
--
You are receiving this mail because:
You are watching all bug changes.
