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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 2489 Actions

    Problem Report Number 2489
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0676
    Raised 2005-11-23 16:15
    Updated 2005-11-24 18:34
    Published 2005-11-24 18:34
    Product Standard X Window System Display
    Certification Program The Open Brand certification program
    Test Suite VSW version 5.1.5
    Test Identification /tset/Xt13/tmalloc/Test{2}
    /tset/Xt13/tcalloc/Test{2}
    /tset/Xt13/trealloc/Test{3}
    Problem Summary Three VSW5 test-cases regress on the ffb3 framebuffer on SPARC platform
    machine running Solaris 10 FCS with 4GB+ of RAM.
    Problem Text Three VSW5 test-cases regress on the ffb3 framebuffer.

    The regressions appear only in testing the 64-bit binary of vsw on a
    SPARC machine with 4GB of RAM + swap; tests with the 32-bit binary of
    vsw do not show the failure. In all three cases, the XToolkit Memory
    Manager is expected to return an error message and does not do so. We
    originally suspected that this was a libXt bug but now we want to file
    it as a VSW test suite difficiency.

    When running the test suite on a machine with more than 4GB of RAM +
    swap, so that XtMalloc(232-1) can return because it can actually
    allocate that much memory (which the test suite designers seemed to
    assume was impossible - which it was back when the test suite was
    originally written on 32-bit machines).

    These 3 VSW tests pass on a SPARC machine with lower RAM (only 128MB).
    Test Output VSW output from the failing tests follows:
    --
    200|1853 2 14:27:37|TP Start
    520|1853 2 00011473 1 1|VSW5TESTSUITE PURPOSE 2
    520|1853 2 00011473 1 2|Assertion XtMalloc-2.(A)
    520|1853 2 00011473 1 3|When there is insufficient memory to allocate
    the requested
    520|1853 2 00011473 1 4|block a call to char *XtMalloc(size) shall issue an
    520|1853 2 00011473 1 5|allocError error and return NULL.
    520|1853 2 00011477 1 1|PREP: Initialize toolkit, Open display and
    Create topLevel root widget
    520|1853 2 00011477 1 2|TRACE: Set up the XtToolkitError handler
    520|1853 2 00011477 1 3|TRACE: Set up widget tree of depth eight (8)
    return panedw widget
    520|1853 2 00011477 1 4|TRACE: Create boxw1 widget in panedw widget
    520|1853 2 00011477 1 5|TRACE: Create rowcolw widget in boxw1 widget
    520|1853 2 00011477 1 6|TRACE: Create push button gadget `Quit' in
    rowcolw widget
    520|1853 2 00011477 1 7|TRACE: Add callback procedure DestroyTree to
    push button gadget `Quit'
    520|1853 2 00011477 1 8|TRACE: Get the label widget name
    520|1853 2 00011477 1 9|TRACE: Create label widget `Xt Function:
    XtMalloc' in boxw1 widget
    520|1853 2 00011477 1 10|TRACE: Register procedure DestroyTree to handle
    events to rowcolw widget
    520|1853 2 00011477 1 11|TRACE: Create boxw2 widget in panedw widget
    520|1853 2 00011477 1 12|TRACE: Set the height and width of boxw2 widget
    520|1853 2 00011477 1 13|PREP: Create windows for widgets and map them
    520|1853 2 00011477 1 14|PREP: Set up toolkit handler for XtMalloc failure
    520|1853 2 00011477 1 15|PREP: Determine largest malloc
    520|1853 2 00011477 1 16|PREP: Allocate that much and the check over the
    limit XtMalloc calls XtErrorMsg
    520|1853 2 00011477 1 17|ERROR: XtMalloc could still allocate -1 bytes
    520|1853 2 00011477 1 18|CLEANUP: Free memory
    520|1853 2 00011477 1 19|ERROR: XtMalloc did not generate toolkit error
    message220|1853 2 1 14:27:37|FAIL
    410|1853 2 1 14:27:37|IC End

    --
    520|1855 2 00011486 1 1|VSW5TESTSUITE PURPOSE 2
    520|1855 2 00011486 1 2|Assertion XtCalloc-2.(A)
    520|1855 2 00011486 1 3|When there is insufficient memory to allocate
    the requested
    520|1855 2 00011486 1 4|block a call to char *XtCalloc(num, size) shall
    issue an520|1855 2 00011486 1 5|allocError error and return NULL.
    520|1855 2 00011490 1 1|PREP: Initialize toolkit, Open display and
    Create topLevel root widget
    520|1855 2 00011490 1 2|TRACE: Set up the XtToolkitError handler
    520|1855 2 00011490 1 3|TRACE: Set up widget tree of depth eight (8)
    return panedw widget
    520|1855 2 00011490 1 4|TRACE: Create boxw1 widget in panedw widget
    520|1855 2 00011490 1 5|TRACE: Create rowcolw widget in boxw1 widget
    520|1855 2 00011490 1 6|TRACE: Create push button gadget `Quit' in
    rowcolw widgt
    520|1855 2 00011490 1 7|TRACE: Add callback procedure DestroyTree to
    push butto gadget `Quit'
    520|1855 2 00011490 1 8|TRACE: Get the label widget name
    520|1855 2 00011490 1 9|TRACE: Create label widget `Xt Function:
    XtCalloc' in bxw1 widget
    520|1855 2 00011490 1 10|TRACE: Register procedure DestroyTree to handle
    eventsto rowcolw widget
    520|1855 2 00011490 1 11|TRACE: Create boxw2 widget in panedw widget
    520|1855 2 00011490 1 12|TRACE: Set the height and width of boxw2 widget
    520|1855 2 00011490 1 13|PREP: Create windows for widgets and map them
    520|1855 2 00011490 1 14|PREP: Set up toolkit handler for XtCalloc failure
    520|1855 2 00011490 1 15|PREP: Determine largest malloc
    520|1855 2 00011490 1 16|PREP: Over the limit XtCalloc should call
    XtErrorMessae
    520|1855 2 00011490 1 17|ERROR: XtCalloc did not generate toolkit error
    message520|1855 2 00011490 1 18|CLEANUP: Free memory
    220|1855 2 1 14:27:40|FAIL
    410|1855 2 1 14:27:40|IC End
    --
    200|1857 3 14:27:41|TP Start
    520|1857 3 00011499 1 1|VSW5TESTSUITE PURPOSE 3
    520|1857 3 00011499 1 2|Assertion XtRealloc-3.(A)
    520|1857 3 00011499 1 3|When there is insufficient memory to allocate
    the requested
    520|1857 3 00011499 1 4|block a call to char *XtRealloc(ptr, num) shall
    issue an
    520|1857 3 00011499 1 5|allocError error and return NULL.
    520|1857 3 00011504 1 1|PREP: Initialize toolkit, Open display and
    Create topLevel root widget
    520|1857 3 00011504 1 2|TRACE: Set up the XtToolkitError handler
    520|1857 3 00011504 1 3|TRACE: Set up widget tree of depth eight (8)
    return panedw widget
    520|1857 3 00011504 1 4|TRACE: Create boxw1 widget in panedw widget
    520|1857 3 00011504 1 5|TRACE: Create rowcolw widget in boxw1 widget
    520|1857 3 00011504 1 6|TRACE: Create push button gadget `Quit' in
    rowcolw widget
    520|1857 3 00011504 1 7|TRACE: Add callback procedure DestroyTree to
    push button gadget `Quit'
    520|1857 3 00011504 1 8|TRACE: Get the label widget name
    520|1857 3 00011504 1 9|TRACE: Create label widget `Xt Function:
    XtRealloc' in boxw1 widget
    520|1857 3 00011504 1 10|TRACE: Register procedure DestroyTree to handle
    events to rowcolw widget
    520|1857 3 00011504 1 11|TRACE: Create boxw2 widget in panedw widget
    520|1857 3 00011504 1 12|TRACE: Set the height and width of boxw2 widget
    520|1857 3 00011504 1 13|PREP: Create windows for widgets and map them
    520|1857 3 00011504 1 14|PREP: Set up toolkit handler for XtRealloc failure
    520|1857 3 00011504 1 15|PREP: Determine largest realloc
    520|1857 3 00011504 1 16|TEST: Allocate memory then verify over the
    limit XtRealloc calls error handler
    520|1857 3 00011504 1 17|CLEANUP: Free memory
    520|1857 3 00011504 1 18|ERROR: XtRealloc did not call error handler
    220|1857 3 1 14:27:42|FAIL
    410|1857 3 1 14:27:42|IC End

    Review Information

    Review Type TSMA Review
    Start Date 2005-11-23 16:15
    Last Updated 2005-11-23 19:16
    Completed 2005-11-23 19:16
    Status Complete
    Review Recommendation Rejected (REJ)
    Review Response Since the system running the test suite has at least one shell which
    provides a ulimit builtin which can set memory limits, it should be a
    simple matter to run the tests with a suitable memory limit in effect
    (e.g. a heap size limit or virtual memory size limit) in order to
    prevent these test failures.

    The VSW user guide should be updated to document that setting such a
    limit is required on systems where more than SIZE_MAX bytes of memory
    are available to the test processes.

    Review Type SA Review
    Start Date 2005-11-23 19:16
    Last Updated 2005-11-24 06:27
    Completed 2005-11-24 06:27
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion The TSMA has identified a work around and thus this PR is rejected as
    a TSD

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority