From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: [RFC] File-I/O, target access to host file system via gdb remote protocol enhancement
Date: Wed, 26 Feb 2003 21:19:00 -0000 [thread overview]
Message-ID: <3E5D2FF4.1040108@redhat.com> (raw)
In-Reply-To: <20021112212526.GA28814@nevyn.them.org>
>
> I like this one too; but I'm not sure that I like linking it to the
> remote-syscall interface. Implementation-wise, that's the most useful
> method for a stub like RedBoot; but for a larger system like gdbserver,
> it's useful to allocate the program a normal pseudo-terminal as if it
> had a console. And to do character rather than line I/O.
>
> As I'm sure Andrew will remind me, my suggestion doesn't fit the
> current remote protocol very well; it's not synchronous enough for one
> thing. So don't take this as an objection, and I'll come back to
> proper remote console support a little later. This'll be a nice
> starting point.
Just FYI. The protocol doesn't preclude doing character IO and doesn't
preclude the remote end using a pty. The pty problem is that it is more
complex. The debug agent (or GDB, in the case of the MI console) needs
to be able to juggle events from multiple sources (wait and i/o).
Anyway, if the overhead of character i/o proves to be too great then a
refinement can be made.
Andrew
prev parent reply other threads:[~2003-02-26 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 4:14 Corinna Vinschen
2002-11-11 22:01 ` [RFC] File-I/O, target access to host file system via gdb , " Eli Zaretskii
2002-11-12 0:40 ` Corinna Vinschen
2002-11-12 13:24 ` [RFC] File-I/O, target access to host file system via gdb " Daniel Jacobowitz
[not found] ` <20021113143522.T10395@cygbert.vinschen.de>
2002-11-13 6:30 ` Daniel Jacobowitz
2002-11-13 6:52 ` Corinna Vinschen
2002-11-13 7:08 ` Daniel Jacobowitz
2002-11-13 7:44 ` Corinna Vinschen
2003-02-26 21:19 ` Andrew Cagney [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=3E5D2FF4.1040108@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.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