Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Eliminate use of deprecated_register_bytes() from remote.c
Date: Mon, 02 May 2005 19:39:00 -0000	[thread overview]
Message-ID: <20050502123908.2cc59dde@ironwood.lan> (raw)
In-Reply-To: <4272BC49.5060801@redhat.com>

On Fri, 29 Apr 2005 15:59:21 -0700
Michael Snyder <msnyder@redhat.com> wrote:

> Kevin Buettner wrote:
> 
> > I can think of no reason to continue to over-allocate space for g/G
> > packets in remote.c 
> 
> What if the target returns a longer string?

GDB will print a "Remote packet too long" message.

Do you know of any stubs which return a "g" packet containing pseudo
registers?

Kevin


      reply	other threads:[~2005-05-02 19:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-15 21:32 Kevin Buettner
2005-04-15 21:38 ` Daniel Jacobowitz
2005-04-15 23:12   ` Kevin Buettner
2005-04-27 15:40     ` Daniel Jacobowitz
2005-04-28 18:16       ` Kevin Buettner
2005-04-29 22:59     ` Michael Snyder
2005-05-02 19:39       ` Kevin Buettner [this message]

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=20050502123908.2cc59dde@ironwood.lan \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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