faulty intialization in spiffs_create_object
the pullrequest adds a simple shell script to run valgrind :-) It also fixes: ==25336== Conditional jump or move depends on uninitialised value(s) ==25336== at 0x41220B: _write (test_spiffs.c:208) ==25336== by 0x40E993: spiffs_phys_wr (spiffs_cache.c:215) ==25336== by 0x405622: spiffs_object_append (spiffs_nucleus.c:1436) ==25336== by 0x40B141: spiffs_hydro_write (spiffs_hydrogen.c:450) ==25336== by 0x40B809: SPIFFS_write (spiffs_hydrogen.c:587) ==25336== by 0x41402A: test_create_and_write_file (test_spiffs.c:779) ==25336== by 0x415A8E: __test_lu_check1 (test_check.c:58) ==25336== by 0x428D4F: run_tests (testrunner.c:192) ==25336== by 0x411D08: main (main.c:9) Which may cause sideeffects for various users .... My memory overruns seems to be fixe - here I need just more testing to be shure. Happy testing!
Hi, please use one of SPIFFS_DBG/SPIFFS_GC_DBG/SPIFFS_CACHE_DBG/SPIFFS_CHECK_DBG macro for debug printing instead of direct call to printf
yes, can be done. i am still debugging the software.