[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
test-sigaction vs SA_RESTORER test failure
From: |
Jim Meyering |
Subject: |
test-sigaction vs SA_RESTORER test failure |
Date: |
Mon, 23 Jun 2008 10:12:40 +0200 |
Hi Eric,
I noticed that the coreutils "make check" is failing due to
gnulib's new sigaction test. The buildbot shows it, too:
http://buildbot.proulx.com:9000/amd64 gnu-linux/builds/8679/step-test/0
-------------------
FAIL: test-sigaction.log (exit: 134)
====================================
../../gnulib-tests/test-sigaction.c:83: assertion failed
71 int
72 main (int argc, char *argv[])
73 {
74 struct sigaction sa;
75 struct sigaction old_sa;
76 sa.sa_handler = handler;
77 sa.sa_flags = 0;
78 ASSERT (sigemptyset (&sa.sa_mask) == 0);
79 ASSERT (sigaction (SIGABRT, &sa, NULL) == 0);
80 ASSERT (raise (SIGABRT) == 0);
81 sa.sa_flags = SA_RESETHAND | SA_NODEFER;
82 ASSERT (sigaction (SIGABRT, &sa, &old_sa) == 0);
83 ASSERT (old_sa.sa_flags == 0);
And the value of old_sa.sa_flags is 0x4000000,
which happens to be SA_RESTORER.
I was about to make a snapshot, now that coreutils uses
the "open" module to address a recent truncate test failure,
but will hold off until this is fixed.