I was probably wrong -- it seems this is not related to running as restricted user per se.
Using ldd shows no reference to libgcc_s in the binary, even if I build from source and explicitly add '-lgcc_s' to the linker command line. strace shows no signs of using libgcc_s unless put into the preload environment. And ntpd always comes to a grinding halt when not run as root unless the preload environment is used. Running as root does not crash just by lucky chance, I think.
I get the same results with gcc-4.7 and gcc-4.8 on a freshly installed x64/amd64 Saucy.
As a workaround, I put libgcc_s.so.1 into /etc/ld.so.preload, since this should help most applications that run into this problem. Though this only cures the symptom: It's still not clear WHY there is no reference to the SO in the binary... Could there be some toolchain trouble?
I was probably wrong -- it seems this is not related to running as restricted user per se.
Using ldd shows no reference to libgcc_s in the binary, even if I build from source and explicitly add '-lgcc_s' to the linker command line. strace shows no signs of using libgcc_s unless put into the preload environment. And ntpd always comes to a grinding halt when not run as root unless the preload environment is used. Running as root does not crash just by lucky chance, I think.
I get the same results with gcc-4.7 and gcc-4.8 on a freshly installed x64/amd64 Saucy.
As a workaround, I put libgcc_s.so.1 into /etc/ld.so.preload, since this should help most applications that run into this problem. Though this only cures the symptom: It's still not clear WHY there is no reference to the SO in the binary... Could there be some toolchain trouble?