| commit | 7e888741d13e66b6b343b8f0839621107c5a2962 | |
| author | Mike Dunn <mikedunn@newsguy.com> | |
| Sun, 19 Sep 2010 21:35:46 +0000 (19 14:35 -0700) | ||
| committer | Øyvind Harboe <oyvind.harboe@zylin.com> | |
| Mon, 20 Sep 2010 07:21:12 +0000 (20 09:21 +0200) | ||
| tree | 55d5080c102cf9815f1c3610a1730340d41c8f83 | treesnapshot (tar.gz zip) |
| parent | 60501bb0fb0cb69f66ebb3ce3b64b69f3cadf4ff | commitdiff |
xscale: bp/wp: additional LOG_ERROR on failure
Hi everyone,
Added more LOG_ERROR messsages to watchpoint and breakpoint code, given that the
infrastructure no longer interprets returned error codes. Also changed
existing LOG_INFO and LOG_WARNING to LOG_ERROR for cases where an error is
returned.
Note that the check of the target state is superflous, since the infrastruture
code currently checks this before calling target code. Is this being
reconsidered as well? Also, should we stop returning anything other than
ERROR_OK and ERROR_FAIL?
Comments gratefully received.
Thanks,
Mike
Signed-off-by: Mike Dunn <mikedunn@newsguy.com>
Hi everyone,
Added more LOG_ERROR messsages to watchpoint and breakpoint code, given that the
infrastructure no longer interprets returned error codes. Also changed
existing LOG_INFO and LOG_WARNING to LOG_ERROR for cases where an error is
returned.
Note that the check of the target state is superflous, since the infrastruture
code currently checks this before calling target code. Is this being
reconsidered as well? Also, should we stop returning anything other than
ERROR_OK and ERROR_FAIL?
Comments gratefully received.
Thanks,
Mike
Signed-off-by: Mike Dunn <mikedunn@newsguy.com>
| src/target/xscale.c | diffblobblamehistory |