No ability to display errors if the GDB returned data is "bad"

[acotty]

There is no ability to display error messages when the GDB memory result is bad.

[acotty]

I have fixed this locally, but I had to modify the C::B source to implement the fix.

[bluehazzard]

Yea, this definitely has to be implemented.
We need some mechanism to report errors from memory watch to plugin. I think this should be possible without much changes?

[Edit:]
i think a flag in the watch is enough? An possibly an additional error String...
This could be extended to normal watches also...

[acotty]

In my local source I added the following flag for this:
bool m_raw_value_is_message; // True if the m_raw_value is a message instead of data

And the following two functions to access it:
bool GetIsValueErrorMessage() override;
void SetIsValueErrorMessage(bool value) override;

[bluehazzard]

Yea, i was thinking about something like that....

[acotty]

The changes for this are in PR#4, but I have not modified the GDB annotations plugin to generate any errors and as such the framework is there once the ticket and PR are merged, but GDB needs to be modified.