Server error reporting #3
Description
About
Currently if an API call to the server fails it fails silently and the client (debugger) is not informed about issue.
Notes
Protocol version needs to be bumped to 3
How it would work
Error reporting packets would be included in a specific region of the allocated message types located after the newly created DEBUGGER_MESSAGE_MAX_NORM enum. The client would check if the incoming packet ID is over the normal range and if so invoke the error reporting function.
Example
# Try to memset something with DEBUGGER_MESSAGE_MEMORY_SET
%2:20:40:[Failed to allocate memory copy source: Type database does not provide a buffer allocator]