Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jon Ringle <jon.ringle@comdial.com>
To: gdb@sources.redhat.com
Subject: Re: minimal stub? (GDB Remote Serial Protocol)
Date: Sat, 24 Jan 2004 00:55:00 -0000	[thread overview]
Message-ID: <200401231955.12261.jon.ringle@comdial.com> (raw)
In-Reply-To: <OLEAKFPBCAKCNMFIJHADKEFIDDAA.kamarshi@broadcom.com>

On Friday 23 January 2004 06:06 pm, Vijay Kamarshi wrote:
> Hi all,
>
> I am planning on using GDB to debug a remote processor running a debug
> stub. It is quite concerning to me that the remote protocol document is
> out-of-date.  Is it that easy to figure out what the protocol is by
> experimentation?  For example if the GDB host sends a stream of commands to
> the remote processor and it mis-interprets the first one, is the host not
> going to just quit on that?  That would make the experimentation process
> pretty long!
>
> I am puzzled:
> 1) are there no people out there who have this protocol figured out?  I
> would appreciate at least a starting point!
> 2) are all the commands in the remote protocol document out of date or just
> some of them?
>
> Any help would be gratefully received.
>
> -Vijay Kamarshi
> PS:  I heard that one way of figuring out this remote protocol is to peer
> deeply into gdbserver, but people have warned me that it is a pretty hairy
> piece of code.

Hi Vijay,

A while back I backported an arm kgdb patch for kernel 2.4.19 to a target 
based on kernel 2.2.16 found at:
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=1335/1

It may be helpful.

Jon


  reply	other threads:[~2004-01-24  0:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 23:16 Németh Márton
2004-01-23  0:45 ` Daniel Jacobowitz
2004-01-23 20:49 ` Andrew Cagney
2004-01-23 23:06   ` Vijay Kamarshi
2004-01-24  0:55     ` Jon Ringle [this message]
2004-01-26 18:54       ` Vijay Kamarshi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200401231955.12261.jon.ringle@comdial.com \
    --to=jon.ringle@comdial.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox