From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, eliz@gnu.org
Subject: Re: [rfc/rfa] [3/4] SPU enhancements: gdbserver support
Date: Mon, 04 Jun 2007 19:54:00 -0000 [thread overview]
Message-ID: <20070604195349.GC23516@caradoc.them.org> (raw)
In-Reply-To: <200706021933.l52JXTJX005551@d12av02.megacenter.de.ibm.com>
On Sat, Jun 02, 2007 at 09:33:29PM +0200, Ulrich Weigand wrote:
> Hello,
>
> this patch, implemented by Markus Deuling, extends TARGET_OBJECT_SPU
> support to remote gdbserver debugging.
>
> This is done by extended the remote protocol by two new packet types,
> qXfer:spu:read and qXfer:spu:write. In addition, the patch contains
> the following changes to remote packet support:
The TARGET_OBJECT_SPU support looks fine. I don't really like either
of these changes, though.
> - It adds a "length" argument to qXfer::write type packets. This is
> to make parsing of the packet easier, and to bring it in line with
> the 'X' packet format. (It also provides a bit of extra redundancy
> to detect transmission problems.)
It adds another case that stubs need to check for (length != length of
supplied data), and it's redundant. I have some code already written
to generate and parse binary packets without a specified length, if
you'd like me to post it. It's for the project I'm going to submit
once I finish with shared library lists - file transfer through
gdbserver.
I think more redundancy is not what we need in an already chatty
protocol :-) And anyone using this to debug an SPU is probably going
to do so over a reliable link (pipe or TCP socket).
> - The remote_read_qxfer attempts to cache received end-of-object
> packets. However, this is a problem for some spufs objects as
> they can start out with no content (length zero), and acquire
> actual content later on. If remote_read_qxfer has already cache
> an end-of-object at lenght zero, future re-reads of the object
> will always return zero even if the object by now has actual
> content. To fix this we've added a CACHEABLE flag to the
> function and use it to disable the cache for spufs objects.
How about this simpler fix?
- if (rs->buf[0] == 'l')
+ if (rs->buf[0] == 'l' && offset + i > 0)
It's only supposed to trigger for the next part of the same read
operation. If we got no bytes, then the operation is already over.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-04 19:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 19:33 Ulrich Weigand
2007-06-02 20:33 ` Eli Zaretskii
2007-06-03 13:28 ` Ulrich Weigand
2007-06-03 16:44 ` Eli Zaretskii
2007-06-04 13:58 ` Ulrich Weigand
2007-06-04 19:19 ` Eli Zaretskii
2007-06-04 20:02 ` Ulrich Weigand
2007-06-04 19:54 ` Daniel Jacobowitz [this message]
2007-06-04 20:05 ` Ulrich Weigand
2007-06-04 20:10 ` Daniel Jacobowitz
2007-06-05 18:34 ` Daniel Jacobowitz
2007-06-05 23:02 ` Ulrich Weigand
2007-06-06 17:51 ` Eli Zaretskii
2007-06-12 13:58 ` Daniel Jacobowitz
2007-06-12 14:43 ` 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=20070604195349.GC23516@caradoc.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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