Hello, David Yang, le ven. 27 févr. 2026 20:55:50 +0800, a ecrit: > On Fri, Feb 27, 2026 at 8:00 AM Samuel Thibault <[email protected]> > wrote: > > David Yang, le jeu. 26 févr. 2026 16:17:44 +0800, a ecrit: > > > I'm investigating > > > https://buildd.debian.org/status/package.php?p=libite on the latest > > > debian-hurd.img and found alarm() fire SIGALRM periodically. > > > > You'd want to upgrade the libc0.3 package to get the latest glibc. > > > > > static void sigalrm_handler(int signo) { > > > printf("alarm %ld\n", time(0)); > > > } > > > > > > int main() { > > > signal(SIGALRM, sigalrm_handler); > > > alarm(1); > > > while (1) sleep(3); > > > } > > > > I don't see this issue with libc0.3 2.42-12 > > After reexamining the libite build log and upgrading everything, I > discovered the bug affects only hurd-amd64, not hurd-i386.
Ah, thanks for checking! I found the issue in the 64b extension of sigcode, which was making the setitimer preemptor fail to catch the signal and stop the timer. I have pushed a fix to upstream glibc and debian glibc. Samuel
