From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: eliz@gnu.org
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc v2][4/6] Readlink as file I/O target operation
Date: Mon, 16 Jan 2012 15:03:00 -0000 [thread overview]
Message-ID: <201201161407.q0GE7htU029197@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <E1Rmmcv-0000OE-GV@fencepost.gnu.org> from "Eli Zaretskii" at Jan 16, 2012 08:29:33 AM
Eli Zaretskii wrote:
> > Date: Mon, 16 Jan 2012 13:32:23 +0100 (CET)
> > From: "Ulrich Weigand" <uweigand@de.ibm.com>
> > Cc: gdb-patches@sourceware.org
> > I'll be happy to use "filename" instead, but the currently existing
> > packets (open, unlink) also use "pathname" today. Should those be
> > changed to "filename" too?
>
> In general, yes. But I cannot in good faith ask you to do that as
> part of this patch. So let's make a first small step in this
> 1000-mile journey by using "filename" in just this part. I'll add to
> my todo to fix the rest, if no one beats me to it.
Fair enough. Appended below is the updated doc part of the patch,
just making the pathname -> filename change for readlink.
Thanks,
Ulrich
Index: gdb-head/gdb/doc/gdb.texinfo
===================================================================
--- gdb-head.orig/gdb/doc/gdb.texinfo 2012-01-13 18:44:34.000000000 +0100
+++ gdb-head/gdb/doc/gdb.texinfo 2012-01-16 15:03:17.000000000 +0100
@@ -17450,6 +17450,10 @@ are:
@tab @code{vFile:unlink}
@tab @code{remote delete}
+@item @code{hostio-readlink-packet}
+@tab @code{vFile:readlink}
+@tab Host I/O
+
@item @code{noack-packet}
@tab @code{QStartNoAckMode}
@tab Packet acknowledgment
@@ -36193,6 +36197,16 @@ error occurred.
Delete the file at @var{pathname} on the target. Return 0,
or -1 if an error occurs. @var{pathname} is a string.
+@item vFile:readlink: @var{filename}
+Read value of symbolic link @var{filename} on the target. Return
+the number of bytes read, or -1 if an error occurs.
+
+The data read should be returned as a binary attachment on success.
+If zero bytes were read, the response should include an empty binary
+attachment (i.e.@: a trailing semicolon). The return value is the
+number of target bytes read; the binary attachment may be longer if
+some characters were escaped.
+
@end table
@node Interrupts
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2012-01-16 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 18:16 Ulrich Weigand
2012-01-13 18:29 ` Eli Zaretskii
2012-01-16 13:29 ` Ulrich Weigand
2012-01-16 14:48 ` Eli Zaretskii
2012-01-16 15:03 ` Ulrich Weigand [this message]
2012-01-16 17:18 ` Eli Zaretskii
2012-01-16 15:37 ` Pedro Alves
2012-01-16 17:26 ` Ulrich Weigand
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=201201161407.q0GE7htU029197@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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