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

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1168 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 1168.

Report 1168 Actions

    Problem Report Number 1168
    Submitter's Classification Specification problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0370
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Internationalised System Calls and Libraries Extended (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSU version 4.1.0
    Test Identification CAPIbase/fsigstack 4
    Problem Summary PG4U.00098 This request maintains that the values associated with of ss_onstack semantics may be implementation specific.
    Problem Text
    We believe the behaviour when the ss_onstack member of ss is non-zero
    is vaugely defined in the specification, as far as which stack
    execution should be occurring on.

    Originally in VSU4.0.2 sigstack#4 was verifying that the alternate
    stack was being used. Then a TSD was applied for and granted
    (TSD4U.00023) which references the bsd man pages for sigstack to
    justify that the execution should not be on the alternate stack.

    Clearly the bsd man pages are not one in the same with the speci-
    fication, and should not be used to make a ruling such as this.

    The specification, however, does not make this point clear and
    we believe a PIN should be granted for this assertion.
    Test Output
    TEST CASE: sigstack

    TEST PURPOSE #4
    A call to int sigstack(struct sigstack *ss , struct
    sigstack *oss) when the ss_onstack member of ss is
    non-zero shall indicate to the system that the process
    is executing on the specified stack.
    PREP: Call sigstack(ss, oss) with ss_onstack non-zero
    PREP: Call sigaction() with SA_ONSTACK set
    PREP: Send self SIGTERM
    TEST: Verify alternate stack not used
    ERROR: Auto declaration is on the alternate stack and shouldn't be
    Declared Top of Stack = AE3AEB0
    Declared End of Stack = AE36EB0
    Received Auto Address = AE39080
    4 FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We recommend this request be refused.

    We do not believe that the TSD4U.00023 submitter was trying to
    argue that the BSD spec is normative. He was just trying to
    point out that the sigstack() spec wording was taken from the BSD
    spec, that the intended semantics are the same and that the BSD
    spec states the issue more clearly.

    The sigstack() 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.

    ...

    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.

    Although this could certainly be more clearly worded we believe the
    statement that ss_onstack will be non-zero applies to all sigstack
    structures, not just oss.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority