From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: cagney@gnu.org
Cc: hans-peter.nilsson@axis.com, gdb-patches@sources.redhat.com
Subject: Re: sim/common: pipe syscall support
Date: Thu, 13 Jan 2005 12:11:00 -0000 [thread overview]
Message-ID: <200501131211.j0DCBhLc008048@ignucius.se.axis.com> (raw)
In-Reply-To: <41E3EBC8.3060204@gnu.org> (message from Andrew Cagney on Tue, 11 Jan 2005 10:07:52 -0500)
> Date: Tue, 11 Jan 2005 10:07:52 -0500
> From: Andrew Cagney <cagney@gnu.org>
> Ok (this does feel very low level).
Thanks.
> However, can you also look over the remote file i/o code. For reasons
> of stupidity we've ended up with two slabs of code (remote hosted i/o
> and simulator hosted i/o) doing essentially the same thing.
I am at a loss here: I cannot perform any useful audit here
compared to the simulator I/O. I looked for a while and grepped
through the manual, but couldn't understand how the bits are
connected, so I have to leave that to a real gdb maintainer. At
least it seems as if calls to remote-fileio doesn't end up in
the simulator and so doesn't interfere with pipe support there;
it connects to a the remote packet handler. The remote-fileio
(whatever it's used for?) seems very simple, only the most basic
operations are there and it doesn't immediately seem a candidate
for adding pipe functionality.
> Also, think about how this will work when (yes you can laugh) GDB
> becomes properly event driven (or failing that multi-threaded).
The simulator vs. gdb interface would have to get thread
support. It doesn't seem like there are framework bits at the
moment.
brgds, H-P
next prev parent reply other threads:[~2005-01-13 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 7:32 Hans-Peter Nilsson
2005-01-11 15:09 ` Andrew Cagney
2005-01-13 12:11 ` Hans-Peter Nilsson [this message]
2005-02-09 16:46 ` 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=200501131211.j0DCBhLc008048@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@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