| Problem with BYTE_CANNOT_READ in Memory Monitors GUIs [message #1106030] |
Tue, 10 September 2013 11:32 |
 Daniel Codres
Messages: 2
Registered: September 2013 |
Junior Member |
|
|
Before submitting this to the Bugzilla I want to check if it is a bug or we are misusing the Memory Service, maybe someone could help.
Our memory has some areas that aren't accessible at byte level (e.g. protected) so the agent sends back an error report plus an array of error addresses objects as documented on:
http://git.eclipse.org/c/tcf/org.eclipse.tcf.git/plain/docs/TCF%20Service%20-%20Memory.html
⇒ { "addr" : <int: range starting address> , "size" : <int: range length in bytes> , "stat" : <int: status code> , "msg" : <object: error description> }
These locations we are marking as BYTE_CANNOT_READ, providing all parameters into the error address list (addr, size, stat and msg)
The thing works somehow, but the problem is that the TCF GUI is unnecessarily incrementing the StartBound asking the agent for the content until the invalid bytes are not in the request window.
This results to a read that's very slow. After finally ending reading the GUI displays the ?? on all packets that included the invalid read.
Does someone experienced such a problem?
|
|
|
Powered by
FUDForum. Page generated in 0.23724 seconds
] 
Search
Help
Register
Login
Home
