When breakpoints intersect a section, process->WriteMemory returns 0 without setting the error, LoadInMemory breaks execution and returns this error, but client code treat it as success.
Just added setting of error status for this case.
Applied clang-format.
If WriteMemory is not setting the error in some case, it seem more logical to properly handle it there instead of putting this specific error message here.