HomeAbout Us A-Z IndexSearch * Contact Us Register LoginPress Shop

The Open Brand -- Problem Reporting and Interpretations System


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


Report 1146 Actions


    Problem Report Number 1146
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0348
    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.1
    Test Identification base/scalb 1
    Problem Summary PG4U.00123 This IR claims that a SIGFPE is allowable in this test.
    Problem Text
    On our platform, after a SIGFPE is generated for a reason other
    than raise() or kill(), (specifically division by zero in the
    scalb #1 assertion) we do not return to the next sequential
    instruction. This is a change from the previous (branded) release
    of our product, but we believe it is a conforming behaviour based
    on the following bullet taken from the Signal Actions section under
    sigaction():

    "The behaviour of a process is undefined after it returns normally
    from a signal-catching function for a SIGBUS, SIGFPE, SIGILL or
    or SIGSEGV signal that was not generated by kill() or raise()."

    Test Output
    10|4055 /tset/CAPIbase/fscalb/fscalb1 04:09:17|TC Start, scenario ref 105-1818
    15|4055 1.10 9|TCM Start
    400|4055 1 1 04:09:23|IC Start
    200|4055 1 04:09:23|TP Start
    520|4055 1 268435466 1 1|SPEC1170TESTSUITE CASE 1
    520|4055 1 268435466 1 2|A call to double scalb(double x, double n) shall
    520|4055 1 268435466 1 3|return x * rn where r is the radix of the machine's
    520|4055 1 268435466 1 4|floating-point arithmetic.
    520|4055 1 1040187411 1 1|TEST: scalb() returns correct value
    520|4055 1 1040187411 1 2|INFO: Spurious SIGFPE generated by scalb
    520|4055 1 268435466 2 1|ERROR: TEST TERMINATED DUE TO SIGFPE SIGNAL (8)
    220|4055 1 1 04:09:27|FAIL
    410|4055 1 1 04:09:27|IC End

    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.

    The submitter is correct in stating that the behavior of a
    process is undefined after returning from a SIGFPE. But the real
    issue here is why the SIGFPE is being raised in the first place.

    We believe there are no division by zero or illegal arithmetic
    operations in the test, so a SIGFPE signal should not occur on a
    conforming implementation.

    So the test is not expecting a SIGFPE, it merely traps it as part
    of a robust error recovery scheme.

    It seems likely that the signal is being generated by one of the
    implementation's library functions. If so, it is the implementations
    responsibility to avoid or recover from the situation causing the signal.

    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