IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Jun 3, 2004, 4:08:42 PM (22 years ago)
Author:
desonia
Message:

:q

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/psLib/test/sysUtils/verified/tst_psMemory.stderr

    r846 r848  
    1717 <DATE> <TIME> <HOST> |I|TPOutOfMemory  |Upon requesting more memory than is available, psalloc shall call the psMemExhaustedCallback.
    1818 <DATE> <TIME> <HOST> |I|TPOutOfMemoryExhaustedCallback|Custom MemExhaustedCallback was invoked.
    19  <DATE> <TIME> <HOST> |A|p_psAlloc      |Failed to allocate 2147483647 bytes at tst_psMemory.c:170
     19 <DATE> <TIME> <HOST> |A|p_psAlloc      |Failed to allocate 4294966295 bytes at tst_psMemory.c:170
    2020
    2121---> TESTPOINT PASSED (psMemory{450-TPOutOfMemory} | tst_psMemory.c)
     
    5959 <DATE> <TIME> <HOST> |I|TPcheckLeaks   |following psMemCheckLeaks call should produce one instance.
    6060                   file:line ID
    61          tst_psMemory.c:333  1
     61         tst_psMemory.c:330  1
    6262 <DATE> <TIME> <HOST> |I|TPcheckLeaks   |Testing psMemCheckLeaks again with a different leak location
    6363 <DATE> <TIME> <HOST> |I|TPcheckLeaks   |following psMemCheckLeaks call should produce one error.
    6464                   file:line ID
    65          tst_psMemory.c:363  11
     65         tst_psMemory.c:360  11
    6666 <DATE> <TIME> <HOST> |I|TPcheckLeaks   |Testing psMemCheckLeaks again with multiple leak locations.
    6767 <DATE> <TIME> <HOST> |I|TPcheckLeaks   |following psMemCheckLeaks call should produce two errors.
    6868                   file:line ID
    69          tst_psMemory.c:391  16
    70          tst_psMemory.c:391  14
     69         tst_psMemory.c:388  16
     70         tst_psMemory.c:388  14
    7171
    7272---> TESTPOINT PASSED (psMemory{454-TPcheckLeaks} | tst_psMemory.c)
Note: See TracChangeset for help on using the changeset viewer.