IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Aug 2, 2004, 9:43:23 AM (22 years ago)
Author:
desonia
Message:

adjusted output precision to allow tests to pass on x86_64, etc.

File:
1 edited

Legend:

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

    r1255 r1365  
    1717 <DATE> <TIME> |<HOST>|I|  TPOutOfMemory|Upon requesting more memory than is available, psalloc shall call the psMemExhaustedCallback.
    1818 <DATE> <TIME> |<HOST>|I|TPOutOfMemoryEx|Custom MemExhaustedCallback was invoked.
    19  <DATE> <TIME> |<HOST>|A|      p_psAlloc|Failed to allocate 4294966295 bytes at tst_psMemory.c:210
     19 <DATE> <TIME> |<HOST>|A|      p_psAlloc|Failed to allocate 4294966295 bytes at tst_psMemory.c:206
    2020
    2121---> TESTPOINT PASSED (psMemory{outOfMemory} | tst_psMemory.c)
     
    2828
    2929 <DATE> <TIME> |<HOST>|I|TPReallocOutOfM|Upon requesting more memory than is available, psRealloc shall call the psMemExhaustedCallback.
    30  <DATE> <TIME> |<HOST>|A|    p_psRealloc|Failed to reallocate -1001 bytes at tst_psMemory.c:175
     30 <DATE> <TIME> |<HOST>|A|    p_psRealloc|Failed to reallocate -1001 bytes at tst_psMemory.c:171
    3131
    3232---> TESTPOINT PASSED (psMemory{reallocOutOfMemory} | tst_psMemory.c)
     
    7070 <DATE> <TIME> |<HOST>|I|   TPcheckLeaks|following psMemCheckLeaks call should produce one instance.
    7171                   file:line ID
    72          tst_psMemory.c:360  1
     72         tst_psMemory.c:356  1
    7373 <DATE> <TIME> |<HOST>|I|   TPcheckLeaks|Testing psMemCheckLeaks again with a different leak location
    7474 <DATE> <TIME> |<HOST>|I|   TPcheckLeaks|following psMemCheckLeaks call should produce one error.
    7575                   file:line ID
    76          tst_psMemory.c:390  11
     76         tst_psMemory.c:386  11
    7777 <DATE> <TIME> |<HOST>|I|   TPcheckLeaks|Testing psMemCheckLeaks again with multiple leak locations.
    7878 <DATE> <TIME> |<HOST>|I|   TPcheckLeaks|following psMemCheckLeaks call should produce two errors.
    7979                   file:line ID
    80          tst_psMemory.c:418  16
    81          tst_psMemory.c:418  14
     80         tst_psMemory.c:414  16
     81         tst_psMemory.c:414  14
    8282
    8383---> TESTPOINT PASSED (psMemory{checkLeaks} | tst_psMemory.c)
     
    9292 <DATE> <TIME> |<HOST>|I|TPmemCorruption|psMemCheckCorruption should output an error message and memProblemCallback callback should be called.
    9393 <DATE> <TIME> |<HOST>|E|psMemCheckCorru|Memory Corruption: memory block 1 is corrupted (buffer underflow)
    94  <DATE> <TIME> |<HOST>|I|memProblemCallb|memory callback called for id 1 (psMemCheckCorruption:254).
     94 <DATE> <TIME> |<HOST>|I|memProblemCallb|memory callback called for id 1 (psMemCheckCorruption:260).
    9595
    9696---> TESTPOINT PASSED (psMemory{psMemCorruption} | tst_psMemory.c)
     
    115115 <DATE> <TIME> |<HOST>|I| TPmultipleFree|Next should be an error about multiple freeing.
    116116 <DATE> <TIME> |<HOST>|E|  checkMemBlock|Memory Corruption: memory block 1 was freed but still used.
    117  <DATE> <TIME> |<HOST>|E|memProblemCallb|Block 1 allocated at tst_psMemory.c:530 freed more than once at tst_psMemory.c:535
    118  <DATE> <TIME> |<HOST>|A|memProblemCallb|Detected a problem in the memory system at tst_psMemory.c:535
     117 <DATE> <TIME> |<HOST>|E|memProblemCallb|Block 1 allocated at tst_psMemory.c:526 freed more than once at tst_psMemory.c:531
     118 <DATE> <TIME> |<HOST>|A|memProblemCallb|Detected a problem in the memory system at tst_psMemory.c:531
    119119
    120120---> TESTPOINT PASSED (psMemory{multipleFree} | tst_psMemory.c)
Note: See TracChangeset for help on using the changeset viewer.