Checksum generator ExactFile has the function to create checksums for all files within an entire directory and later compare those files with the generated checksum file. (Other checksum generators which I have tried to use do not have the function to compare all files within a directory with their checksum file generated previously.)
However, the latest version of ExactFile seems to be from 2009. Are there any other good checksum generators which include the function to compare all files within a directory with their checksum file generated previously?
I am not knowledgeable in this subject, but since algorithms for generating checksums have not changed since 2009, ExactFile can still be used. But the author of the program says that it is a beta version and that improvements may be made. Therefore, I thought that it is better to find a checksum generator which is not in a beta stage and has been released more recently.
This is not a c++ question. Interesting that you created this account specifically for asking this single question on a c++ forum.
What I find more interesting is that the linguistic syntax you are using such as "which include","generated previously" and preposition usage such as "within" and the overall sentence length[^] strongly imply a native English speaker and not someone from the "Russian Federation" as your profile indicates.
I'm getting a heap corruption error while debugging one
Of my message handling routines
It is on exit from the routine which lead me to think it's something with the stack or local variables
However I have not declared any local variables it's just parameters wparam and lparam
I can try to wrap the code in a try and catch I guess CMemoryException
I don't see any class members for CMemoryException Like line numbers ( line which caused the exception)
BTW wparam is a pointer from tcp/ip message/buffer and lparam is the length
Which I memcpy after doing a new in the routine
I am running 64 bit code
This is a very powerful tool... and you will become a much better engineer if you learn how to use the Windows debugging tools. Note that GFlags is not just for kernelmode... you can enable per-process heap monitoring in usermode processes:
I guess that in a time the message is handled in your main thread the variable sockbuffer might go out of scope. The result - the memory exception.
Is this message is posted from the other (socket) thread?
Anyway, check out this great J.Newcomer essay: WorkerThreads