https://bugs.kde.org/show_bug.cgi?id=462326
--- Comment #6 from Lova <l...@avoidpointer.com> --- Ok, the plot thickens. I realized that the reason why one build (your commit) worked, while the other did not, was the fact that the one I built from the tarball, I had issued "make install" for. This meant that the library and the binary got separated into bin and lib respectively, and I was running the binary from the locally installed bin directory without setting LD_LIBRARY_PATH, and thus it was picking up the globally installed libkgraphviewer.so.2.4.3. In the case of the master build, I was simply running the binary from the bin folder in the build directory, which apparently bundles all cmake target outputs together. So I tried setting LD_LIBRARY_PATH manually to force the built libkgraphviewer.so.2.4.3 to be used... and then both master and even the 2.4.3 tarball worked. Manually copying my built libkgraphviewer.so.2.4.3 to /usr/lib also allowed my installed kgraphviewer to work. I figured it must be something with the way Arch builds the package, but the PKGBUILD could not be any simpler: https://raw.githubusercontent.com/archlinux/svntogit-community/packages/kgraphviewer/trunk/PKGBUILD My next idea was the compiler flags. I checked /etc/makepkg, which sets the following global CXXFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS Compiling with these flags did not make a difference. I could still not get kgraphviewer to crash. Finally, I downloaded the PKGBUILD and ran makepkg manually, and installed my manually built package, just in case there would be something in the makepkg process that sets any flags that I am not aware of. Guess what? It worked wonderfully, no crash at all. So right now, it *seems* like the package on the Arch package mirrors for some reason has this crash. But compiling the source myself from the very same PKGBUILD does not yield the problem. I imagine that this is some kind of downstream problem, so I will report it to Arch Linux instead. -- You are receiving this mail because: You are watching all bug changes.
