|
I recognized this problem and have a patch. It was caused by introduction of new commands between gdb and gdbserver which Linux kernel does not support. Here is the patch.
From c8f99189be0bb84ecdb5657346cddc3a20e0d6bf Mon Sep 17 00:00:00 2001 From: caz yokoyama <caz@xxxxxxxxxxxxxxxxxxx> Date: Fri, 25 Jun 2010 07:45:52 -0700 Subject: [PATCH] Linux kernel does not support several commands. By this modification, break-in to kernel, continue, and quit in gdb work. --- gdb/remote.c | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/gdb/remote.c b/gdb/remote.c index 35d517d..d5c31bf 100644 --- a/gdb/remote.c +++ b/gdb/remote.c @@ -9778,6 +9778,10 @@ remote_get_trace_status (struct trace_status *ts) /* FIXME we need to get register block size some other way */ extern int trace_regblock_size; + /* Linux kernel does not support qTStatus */ + if (interrupt_sequence_mode == interrupt_sequence_break_g) + return -1; + trace_regblock_size = get_remote_arch_state ()->sizeof_g_packet; putpkt ("qTStatus"); @@ -10285,6 +10289,10 @@ remote_upload_trace_state_variables (struct uploaded_tsv **utsvp) struct remote_state *rs = get_remote_state (); char *p; + /* Linux kernel does not support qTfV */ + if (interrupt_sequence_mode == interrupt_sequence_break_g) + return -1; + /* Ask for a first packet of variable definition. */ putpkt ("qTfV"); getpkt (&rs->buf, &rs->buf_size, 0); -- 1.5.4.3
-caz On Mon, Jun 28, 2010 at 7:26 AM, Matt W. Benjamin <matt@xxxxxxxxxxxx> wrote: Hi, -- -caz, yokoyama@xxxxxxxxxxxxxx, caz@xxxxxxxxxxx, 503-804-1028(m)
|
