save errors to flash are not giving details in webinterface. about espeasy HOT 6 CLOSED

I too am running into the "save to flash error" and it's not clear what this means. Some more clarity is definitely needed!

from espeasy.

proving to be a bit more work than expected, adding error checking everywhere and cleanup flashcounting and webgui-feedback.

error checking is very important to prevent very hard to debug problems when someone just has bad flash memory.

from espeasy.

already discovered a bug by these new checks: security.dat was 512 bytes but this is too small for current security struct.

from espeasy.

still have to test this, for now: if i made a mistake, major stuff will be broken :)

from espeasy.

@mvdbro tomorrow i will add -Wall and -Werror to the compiler flag to fix lots of obscure errors. for example:

warning: control reaches end of non-void function [-Wreturn-type]

because warnings where off, i didnt get this error, and i had some strange crashes. for example adding
if (false) { return(""); } crashed, and removing that line didnt crash. after adding a return("") to the end of the function things where fine. that took some hours to debug :P

from espeasy.

saw another issue with save errors, will look at that one.

from espeasy.