ntpd crashes with 'libgcc_s.so.1 must be installed...'

[Juergen Perlinger]

After a few minutes, ntpd crashes with the infamous "libgcc_s.so.1 must be installed for pthread_cancel to work" message.

System Info:

jnperlin@hydra:~$ lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10

jnperlin@hydra:~$ apt-cache policy ntp
ntp:
  Installed: 1:4.2.6.p5+dfsg-3ubuntu2
  Candidate: 1:4.2.6.p5+dfsg-3ubuntu2
  Version table:
 *** 1:4.2.6.p5+dfsg-3ubuntu2 0
        500 http://de.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status

Using strace I finally tracked it down into the runtime library: libgcc_s.so.1 is opened, but the mmap failes with EAGAIN. I was using

# strace -f -o systrace -- ntpd -c /etc/ntp.conf.test -p /var/run/ntpd.pid -g -u 116:125

The interesting lines are:

2631 open("/lib/x86_64-linux-gnu/libgcc_s.so.1", O_RDONLY|O_CLOEXEC <unfinished ...>
2630 <... select resumed> ) = 1 (in [23])
2631 <... open resumed> ) = 4
2630 select(24, [6 7 16 17 18 19 20 21 22 23], NULL, NULL, {0, 0} <unfinished ...>
2631 read(4, <unfinished ...>
2630 <... select resumed> ) = 1 (in [23], left {0, 0})
2631 <... read resumed> "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360*\0\0\0\0\0\0"..., 832) = 832
2630 read(23, <unfinished ...>
2631 fstat(4, <unfinished ...>
2630 <... read resumed> "\0", 32) = 1
2631 <... fstat resumed> {st_mode=S_IFREG|0755, st_size=88408, ...}) = 0
2630 close(24 <unfinished ...>
2631 mmap(NULL, 2184224, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
2630 <... close resumed> ) = 0
2631 close(4 <unfinished ...>
2630 close(23 <unfinished ...>
2631 <... close resumed> ) = 0
2631 open("/dev/tty", O_RDWR|O_NOCTTY|O_NONBLOCK <unfinished ...>
2630 <... close resumed> ) = 0
2631 <... open resumed> ) = 4
2630 select(23, [6 7 16 17 18 19 20 21 22], NULL, NULL, NULL <unfinished ...>
2631 writev(4, [{"libgcc_s.so.1 must be installed "..., 59}], 1) = 59

The complete (gzip'ped) strace output is appended to this bug; the bomb goes off in the last few lines. I filed this against the application where I could track it down.