From: fche@redhat.com (Frank Ch. Eigler)
To: Andrew Cagney <cagney@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: G packet format ...
Date: Thu, 01 Nov 2001 16:51:00 -0000 [thread overview]
Message-ID: <o5wv0uh77t.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <3BEF5CF4.4010201@cygnus.com>
cagney wrote:
: [...] As part of breaking^D^D^Dfixing this, I'd like to introduce a
: new CLI command that allows the user to specify the G packet (and in
: fact the entire remote protocol numbering) at runtime. [...]
I assume the intent is eventually (soon?) to query the remote target
for its own remote-register-spec string. After all, it knows best.
If so, is it a possible problem that the specification string of a
large-register-bank machine may itself be so long as to exceed various
packet-size limits?
- FChE
next prev parent reply other threads:[~2001-11-13 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 9:37 Andrew Cagney
2001-11-01 10:18 ` Daniel Jacobowitz
2001-11-01 10:30 ` Andrew Cagney
2001-11-01 10:58 ` Daniel Jacobowitz
2001-11-05 8:04 ` Andrew Cagney
2001-11-01 12:30 ` Fernando Nasser
2001-11-01 12:51 ` Andrew Cagney
2001-11-01 16:51 ` Frank Ch. Eigler [this message]
2001-11-02 0:37 ` Andrew Cagney
2001-11-05 8:19 ` Andrew Cagney
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=o5wv0uh77t.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=cagney@cygnus.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