Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Paul Bartlett" <paul.bartlett@st.com>
To: <gdb@sources.redhat.com>
Subject: FW: gdbserver, remote serial protocol and endian issues
Date: Wed, 10 Apr 2002 02:50:00 -0000	[thread overview]
Message-ID: <NFBBJFENOKPKFDAKMJGLAEFACCAA.paul.bartlett@st.com> (raw)



-----Original Message-----
From: ac131313@cygnus.com [mailto:ac131313@cygnus.com]
Sent: 09 April 2002 18:14
To: paul.bartlett@st.com
Subject: Re: gdbserver, remote serial protocol and endian issues


> 
> I've spent a good proportion of the day trawling the list
> archives for JT Conklin's stuff.
> 
> I noticed that he was a prolific contributor up to about 16 July
> 2001 and then just disappeared completely.

He was overtaken by other commitments.

> A cursory inspection of remote.c shows that the memory attribute
> changes have made it down to remote_xfer_memory(). I presume
> that all that needs to be done (for remote targets anyhow) is to
> come up with suitable changes to the rsp and propagate the
> parameters through.
> 
> I see that one of JT's last contributions was a suggested
> syntax.

> Does anybody have any opinions on which way to go from here?

Proceduraly or technically?

Proceduraly, the first thing to do is get the GDB community to agree on 
the protocol extension.

Technically, the first thing to do would be the same - without that 
agreement you run the (real) risk of implementing a protocol extension 
that isn't accepted into the GDB source tree.

enjoy,
Andrew




             reply	other threads:[~2002-04-10  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10  2:50 Paul Bartlett [this message]
2002-04-10  3:05 ` Paul Bartlett
  -- strict thread matches above, loose matches on Subject: below --
2002-04-09  9:31 Fw: " Paul Bartlett
2002-04-09 10:16 ` Andrew Cagney
2002-04-08  8:40 Paul Bartlett

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=NFBBJFENOKPKFDAKMJGLAEFACCAA.paul.bartlett@st.com \
    --to=paul.bartlett@st.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