From 31cfaf213b25654043b784fa298d5e41f2e6fff1 Mon Sep 17 00:00:00 2001
From: Daniel Beer <daniel@tortek.co.nz>
Date: Tue, 27 Jul 2010 16:54:08 +1200
Subject: [PATCH] Report halts to gdb as being caused by SIGTRAP.

Reporting a signal number of 0 causes strange behaviour from gdb when
restarting from a breakpoint.
---
 gdb.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gdb.c b/gdb.c
index 6a3c901..72b89a9 100644
--- a/gdb.c
+++ b/gdb.c
@@ -373,7 +373,7 @@ static int run_final_status(struct gdb_data *data)
 		return gdb_send(data, "E00");
 
 	gdb_packet_start(data);
-	gdb_printf(data, "T00");
+	gdb_printf(data, "T05");
 	for (i = 0; i < 16; i++)
 		gdb_printf(data, "%02x:%02x%02x;", i,
 			   regs[i] & 0xff, regs[i] >> 8);
@@ -489,7 +489,7 @@ static int process_gdb_command(struct gdb_data *data, char *buf, int len)
 {
 	switch (buf[0]) {
 	case '?': /* Return target halt reason */
-		return gdb_send(data, "T00");
+		return run_final_status(data);
 
 	case 'z':
 	case 'Z':