diff options
| author | Jason Wessel <jason.wessel@windriver.com> | 2009-04-27 13:20:21 -0500 |
|---|---|---|
| committer | Jason Wessel <jason.wessel@windriver.com> | 2009-12-11 08:43:19 -0600 |
| commit | d625e9c0d706eb43afbf52634d5cecacae1d57cc (patch) | |
| tree | 080cb5ced15c3a0235fc270e9bae2fe8a904bd11 | |
| parent | 8097551d9ab9b9e3630694ad1bc6e12c597c515e (diff) | |
| download | op-kernel-dev-d625e9c0d706eb43afbf52634d5cecacae1d57cc.zip op-kernel-dev-d625e9c0d706eb43afbf52634d5cecacae1d57cc.tar.gz | |
kgdb: continue and warn on signal passing from gdb
On some architectures for the segv trap, gdb wants to pass the signal
back on continue. For kgdb this is not the default behavior, because
it can cause the kernel to crash if you arbitrarily pass back a
exception outside of kgdb.
Instead of causing instability, pass a message back to gdb about the
supported kgdb signal passing and execute a standard kgdb continue
operation.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
| -rw-r--r-- | kernel/kgdb.c | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/kernel/kgdb.c b/kernel/kgdb.c index ca21fe9..8584eac 100644 --- a/kernel/kgdb.c +++ b/kernel/kgdb.c @@ -1210,8 +1210,10 @@ static int gdb_cmd_exception_pass(struct kgdb_state *ks) return 1; } else { - error_packet(remcom_out_buffer, -EINVAL); - return 0; + kgdb_msg_write("KGDB only knows signal 9 (pass)" + " and 15 (pass and disconnect)\n" + "Executing a continue without signal passing\n", 0); + remcom_in_buffer[0] = 'c'; } /* Indicate fall through */ |
