Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org
Subject: [rfc/rfa] [1/4] SPU enhancements: preparation
Date: Sat, 02 Jun 2007 19:31:00 -0000	[thread overview]
Message-ID: <200706021931.l52JVBZQ005084@d12av02.megacenter.de.ibm.com> (raw)

Hello,

this is a small fix in preparation for adding extended SPU query support.
Some files in spufs accessed via the spu_proc_xfer_spu routines in
spu-linux-nat.c and gdbserver/spu-low.c are non-seekable.  Currently,
any attempt to access those at non-zero offset results in a failure.

However, that is a problem when trying to use those files via the
target object mechanism.  For example, the target_read routine will
first read a chunk at offset zero (which succeeds, and in fact is
generally sufficient to retrieve the full contents as the non-seekable
files are small).  But then it attempts a second read at an offset
corresponding to the length of the first chunk read, which now fails.

This patch changes spu_proc_xfer_spu to simply return zero (i.e. no
more data available) on any attempt to access a non-seekable spufs
file at non-zero offset.

Tested on spu-elf in conjunction with the other patches.

Bye,
Ulrich


ChangeLog:

	* spu-linux-nat.c (spu_proc_xfer_spu): Do not return failure when
	accessing non-seekable spufs files.

gdbserver/ChangeLog:

	* spu-low.c (spu_proc_xfer_spu): Do not return failure when
	accessing non-seekable spufs files.


diff -urNp gdb-orig/gdb/gdbserver/spu-low.c gdb-head/gdb/gdbserver/spu-low.c
--- gdb-orig/gdb/gdbserver/spu-low.c	2007-05-10 23:34:34.000000000 +0200
+++ gdb-head/gdb/gdbserver/spu-low.c	2007-06-01 19:21:10.212694495 +0200
@@ -248,7 +248,7 @@ spu_proc_xfer_spu (const char *annex, un
       && lseek (fd, (off_t) offset, SEEK_SET) != (off_t) offset)
     {
       close (fd);
-      return -1;
+      return 0;
     }
 
   if (writebuf)
diff -urNp gdb-orig/gdb/spu-linux-nat.c gdb-head/gdb/spu-linux-nat.c
--- gdb-orig/gdb/spu-linux-nat.c	2007-05-09 01:01:49.000000000 +0200
+++ gdb-head/gdb/spu-linux-nat.c	2007-06-01 19:21:10.362672892 +0200
@@ -250,7 +250,7 @@ spu_proc_xfer_spu (const char *annex, gd
       && lseek (fd, (off_t) offset, SEEK_SET) != (off_t) offset)
     {
       close (fd);
-      return -1;
+      return 0;
     }
 
   if (writebuf)
-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


             reply	other threads:[~2007-06-02 19:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 19:31 Ulrich Weigand [this message]
2007-06-04 19:27 ` Daniel Jacobowitz
2007-06-12 14:40 ` Ulrich Weigand
2007-06-15 15:50 ` Mark Kettenis
2007-06-15 15:54   ` 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=200706021931.l52JVBZQ005084@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --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