pmem / pmdk

Persistent Memory Development Kit
https://pmem.io
Other
1.35k stars 510 forks source link

Test: obj_memops/TEST0: SETUP (all/pmem/debug/memcheck) fails #4369

Closed Greg091 closed 4 years ago

Greg091 commented 4 years ago

ISSUE:

Environment Information

Please provide a reproduction of the bug:

$ ./RUNTESTS obj_memops -m force-enable
obj_memops/TEST0: SETUP (check/pmem/debug/memcheck)
obj_memops/TEST0 failed with Valgrind. See memcheck0.log. Last 20 lines below.
obj_memops/TEST0 memcheck0.log ==805349==    by 0x406DFA: main (obj_memops.c:653)
obj_memops/TEST0 memcheck0.log ==805349== 
obj_memops/TEST0 memcheck0.log ==805349== Conditional jump or move depends on uninitialised value(s)
obj_memops/TEST0 memcheck0.log ==805349==    at 0x4297B8: ulog_by_offset (ulog.c:66)
obj_memops/TEST0 memcheck0.log ==805349==    by 0x429808: ulog_next (ulog.c:80)
obj_memops/TEST0 memcheck0.log ==805349==    by 0x429EFE: ulog_rebuild_next_vec (ulog.c:257)
obj_memops/TEST0 memcheck0.log ==805349==    by 0x4191AF: operation_new (memops.c:201)
obj_memops/TEST0 memcheck0.log ==805349==    by 0x405778: test_redo (obj_memops.c:189)
obj_memops/TEST0 memcheck0.log ==805349==    by 0x406DFA: main (obj_memops.c:653)
obj_memops/TEST0 memcheck0.log ==805349== 
obj_memops/TEST0 memcheck0.log ==805349== 
obj_memops/TEST0 memcheck0.log ==805349== HEAP SUMMARY:
obj_memops/TEST0 memcheck0.log ==805349==     in use at exit: 0 bytes in 0 blocks
obj_memops/TEST0 memcheck0.log ==805349==   total heap usage: 35,611 allocs, 35,586 frees, 60,259,803 bytes allocated
obj_memops/TEST0 memcheck0.log ==805349== 
obj_memops/TEST0 memcheck0.log ==805349== All heap blocks were freed -- no leaks are possible
obj_memops/TEST0 memcheck0.log ==805349== 
obj_memops/TEST0 memcheck0.log ==805349== Use --track-origins=yes to see where uninitialised values come from
obj_memops/TEST0 memcheck0.log ==805349== For lists of detected and suppressed errors, rerun with: -s
obj_memops/TEST0 memcheck0.log ==805349== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
RUNTESTS: stopping: obj_memops/TEST0 failed, TEST=check FS=pmem BUILD=debug

How often bug is revealed: (always, often, rare): always

Actual behavior:

Test fails.

Expected behavior:

The test should pass.

Details

pmemobj0.log memcheck0.log pmem0.log

Additional information about Priority and Help Requested:

Are you willing to submit a pull request with a proposed change? (Yes, No)

Requested priority: (Showstopper, High, Medium, Low)

Greg091 commented 4 years ago

It still fails. I checked it on 1.8-rc1

Greg091 commented 4 years ago

Logs: pmem0.log pmemobj0.log trace0.log

memcheck0.log out0.log

Greg091 commented 4 years ago

Verified on: 1.8-326-gf60928bff