[kdb] [Kgdb-bugreport] kdb working, but kgdb not? 2.6.35-rc3

[caz yokoyama]

Disregard. I looked back Matt's symptom. His symptom is not the one I
observed. Sorry for bothering you. My sympton is that recednt gdb does not
work with kgdb since Jan 16 2010 include gdb-7.1.
-caz

On Mon, Jun 28, 2010 at 5:33 PM, caz yokoyama <cazyokoyama at gmail.com> wrote:

> 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 at calypso.caztech.com>
>
> 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 at linuxbox.com>wrote:
>
>> Hi,
>>
>> I've been trying out the kdb, kgdb integration on 2.6.35-rc3, and so far,
>> kdb is useable but kgdb not.
>>
>> I have a slightly messy configuration, with virtualbox vm, host pipes, and
>> a tcp pipe connector so that one vm monitors the other.  However, I seem to
>> have no trouble using kdb at 115200.  When I try to use kgdb (and I also
>> rebuilt the kernel with only kgdb enabled), gdb hangs, faults, etc.  The
>> initial reported error is "warning: unrecognized item "timeout" in
>> "qSupported" response."
>>
>> I'm guessing the problem could be the gdb--I'm using fedora 13's 7.1-26.
>>  Can anyone make suggestions?
>>
>> Matt
>>
>> --
>>
>> Matt Benjamin
>>
>> The Linux Box
>> 206 South Fifth Ave. Suite 150
>> Ann Arbor, MI  48104
>>
>> http://linuxbox.com
>>
>> tel. 734-761-4689
>> fax. 734-769-8938
>> cel. 734-216-5309
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> _______________________________________________
>> Kgdb-bugreport mailing list
>> Kgdb-bugreport at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
>>
>
>
>
> --
> -caz, yokoyama at member.fsf.org, caz at caztech.com, 503-804-1028(m)
>
>


-- 
-caz, yokoyama at member.fsf.org, caz at caztech.com, 503-804-1028(m)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.sgi.com/pipermail/kdb/attachments/20100628/ec6d7418/attachment-0001.htm>