From: Corinna Vinschen <vinschen@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: [RFC] File-I/O, target access to host file system via gdb remote protocol enhancement
Date: Wed, 13 Nov 2002 06:52:00 -0000 [thread overview]
Message-ID: <20021113155154.V10395@cygbert.vinschen.de> (raw)
In-Reply-To: <20021113143140.GA7232@nevyn.them.org>
On Wed, Nov 13, 2002 at 09:31:40AM -0500, Daniel Jacobowitz wrote:
> On Wed, Nov 13, 2002 at 02:35:22PM +0100, Corinna Vinschen wrote:
> > On Tue, Nov 12, 2002 at 04:25:26PM -0500, Daniel Jacobowitz wrote:
> > > Ick, 32-bit st_ino... why bother to transfer it if you say "no meaning
> > > for the target"?
> >
> > The point is mainly to have all fields available which a POSIX compliant
> > application may expect.
>
> Right; but you require that the stub convert to host format anyway, so
In case of the stat structure it's always gdb which creates/sends the
structure. The struct is filled by gdb on behalf of the target OS.
I'm not aware of a system call which takes a stat struct as input parameter.
> it seems odd to send the unused members over the wire. I guess they
> might be used someday.
So you'd change st_ino to 64 bit?
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:vinschen@redhat.com
next prev parent reply other threads:[~2002-11-13 14:52 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 [this message]
2002-11-13 7:08 ` Daniel Jacobowitz
2002-11-13 7:44 ` Corinna Vinschen
2003-02-26 21: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=20021113155154.V10395@cygbert.vinschen.de \
--to=vinschen@redhat.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