debug_core,kdb: fix kgdb_connected bit set in the wrong place
Immediately following an exit from the kdb shell the kgdb_connected variable should be set to zero, unless there are breakpoints planted. If the kgdb_connected variable is not zeroed out with kdb, it is impossible to turn off kdb. This patch is merely a work around for now, the real fix will check for the breakpoints. Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
This commit is contained in:
		| @@ -605,13 +605,13 @@ cpu_master_loop: | ||||
| 		if (dbg_kdb_mode) { | ||||
| 			kgdb_connected = 1; | ||||
| 			error = kdb_stub(ks); | ||||
| 			kgdb_connected = 0; | ||||
| 		} else { | ||||
| 			error = gdb_serial_stub(ks); | ||||
| 		} | ||||
|  | ||||
| 		if (error == DBG_PASS_EVENT) { | ||||
| 			dbg_kdb_mode = !dbg_kdb_mode; | ||||
| 			kgdb_connected = 0; | ||||
| 		} else if (error == DBG_SWITCH_CPU_EVENT) { | ||||
| 			dbg_cpu_switch(cpu, dbg_switch_cpu); | ||||
| 			goto cpu_loop; | ||||
|   | ||||
		Reference in New Issue
	
	Block a user