diff options
| author | Mike Dunn <mikedunn@newsguy.com> | 2010-09-12 12:05:07 -0700 |
|---|---|---|
| committer | Øyvind Harboe <oyvind.harboe@zylin.com> | 2010-09-13 19:45:42 +0200 |
| commit | 81e0d4438ec4b4112e28a9e90ba2fc1fb548310b (patch) | |
| tree | cc2493e7ee844649b7433cb384acec1cc13b8bcd /contrib/libdcc/example.c | |
| parent | 8afd2309a4e18b222da189eb51f46339f17201d5 (diff) | |
| download | openocd_libswd-81e0d4438ec4b4112e28a9e90ba2fc1fb548310b.tar.gz openocd_libswd-81e0d4438ec4b4112e28a9e90ba2fc1fb548310b.tar.bz2 openocd_libswd-81e0d4438ec4b4112e28a9e90ba2fc1fb548310b.tar.xz openocd_libswd-81e0d4438ec4b4112e28a9e90ba2fc1fb548310b.zip | |
propagate return status of set_breakpoint() up call chain
Hi everyone,
I figured since I was poking around in the breakpoint code on other arches, I'd
add this change to those arches that don't do it already. This patch propagates
the return code of <arch>_set_breakpoint() up the call stack. This ensures that
the higher layer breakpoint infrastructure is aware that an error ocurred, in
which case the breakpoint is not recorded.
Normally I wouldn't touch code that I can't test, but the code is very
uniform across architectures, and the change is rather benign, so I figured
after careful inspection that it is safe. If the maintainers or others think
this is imprudent, the patch can be dropped.
Also changed the error code to something more appropriate in two cases where
hardware resources are unavailable.
Comments and criticisms of course gratefully received.
Mike
Signed-off-by: Mike Dunn <mikedunn@newsguy.com>
Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
Diffstat (limited to 'contrib/libdcc/example.c')
0 files changed, 0 insertions, 0 deletions