summaryrefslogtreecommitdiff
path: root/payloads/libpayload/include/gdb.h
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2018-10-10 15:54:10 -0700
committerJulius Werner <jwerner@chromium.org>2018-10-12 20:17:40 +0000
commit1bfda7293ac0f06681097a8cd6964d86af0b24ba (patch)
tree112ac84c8f55ad1bae73468c261612e0d19a9677 /payloads/libpayload/include/gdb.h
parent5c0e72ff9952bef2dcb62881ced0d95f8ad9cf1d (diff)
downloadcoreboot-1bfda7293ac0f06681097a8cd6964d86af0b24ba.tar.xz
libpayload: gdb: Factor out gdb_handle_reentrant_exception() from arm32
The arm32 GDB architecture code contains a little hack that allows it to (sort of) correctly deal with a reentrant exception triggered from within the GDB stub. The main logic for this isn't really arm32 specific and could be useful for other architectures as well, so factor it out into a separate function. Change-Id: I3c6db8cecf1e86bba23de6fd2ac9fdf0cf69d3c6 Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://review.coreboot.org/29019 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'payloads/libpayload/include/gdb.h')
-rw-r--r--payloads/libpayload/include/gdb.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/payloads/libpayload/include/gdb.h b/payloads/libpayload/include/gdb.h
index 8147431105..1f50491662 100644
--- a/payloads/libpayload/include/gdb.h
+++ b/payloads/libpayload/include/gdb.h
@@ -77,6 +77,7 @@ void gdb_send_reply(const struct gdb_message *reply);
/* gdb/stub.c */
void gdb_command_loop(uint8_t signal);
+int gdb_handle_reentrant_exception(void);
enum {
GDB_SIG0 = 0, /* Signal 0 */