Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1508 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 1508.

Report 1508 Actions

    Problem Report Number 1508
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0790
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1995-05-26 08:00
    Product Standard Internationalised System Calls and Libraries Extended (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSU version 4.0.2
    Test Identification base/sigstack 4
    Problem Summary TSD4U.00023 Test method is not consistent with spec.
    Problem Text
    The spec states that

    o The value of the ss_onstack member indicates
    whether the process wants the system to use an
    alternate signal stack when delivering signals.

    and further on:

    The value stored in the ss_onstack member of oss will be non-
    zero if the process is currently executing on the alternate
    signal stack.

    Unfortunately the test assumes that this means that setting the
    ss_onstack element to a non-zero value when installing the new
    alternate stack will cause the immediate use of the alternate
    stack for the purpose of catching signals. This is not the case.
    here is an excerpt from the bsd man page for sigstack:

    If nss is not a NULL pointer, sigstack() sets the signal
    stack state to the value in the sigstack() structure pointed
    to by nss. Note: if ss_onstack is non-zero, the system will
    think that the process is executing on the signal stack. If
    nss is a NULL pointer, the signal stack state will be
    unchanged.

    Thus, if ss_onstack is non-zero the system assumes that the
    process is *already* using the alternate stack. In the case of
    the test suite, where ss_onstack is set, the system will *never*
    switch to the alternate stack because it assumes that the
    alternate stack is already in use; which of course it is not.
    Test Output
    520|1 4 31043 1 3|A call to int sigstack(struct sigstack *ss , struct
    520|1 4 31043 1 4|sigstack *oss) when the ss_onstack member of ss is
    520|1 4 31043 1 5|non-zero shall indicate to the system that the process
    520|1 4 31043 1 6|wants the system to use an alternate signal stack when
    520|1 4 31043 1 7|delivering signals.
    520|1 4 31023 1 1|PREP: Call sigstack(ss, oss) with ss_onstack non-zero
    520|1 4 31023 1 2|PREP: Call sigaction() with SA_ONSTACK set
    520|1 4 31023 1 3|PREP: Send self SIGTERM
    520|1 4 31023 1 4|TEST: Verify alternate stack used
    520|1 4 31023 1 5|ERROR: Auto declaration was outside boundaries of declared sta
    ck
    520|1 4 31023 1 6| Declared Top of Stack = 140012ec0
    520|1 4 31023 1 7| Declared End of Stack = 14000aec0
    520|1 4 31023 1 8| Received Auto Address = 11ffff328
    220|1 4 1 15:32:33|FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We agree this is a deficiency in the test suite version(s) listed above.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion
    This is an agreed Test Suite Deficiency.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority