From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "Ulrich Weigand" <uweigand@de.ibm.com>
Subject: Re: [commit, gdbserver] Fix gdbserver on SPU
Date: Fri, 03 Apr 2009 14:47:00 -0000 [thread overview]
Message-ID: <200904031547.59755.pedro@codesourcery.com> (raw)
In-Reply-To: <200904031440.n33Eeh93024037@d12av02.megacenter.de.ibm.com>
On Friday 03 April 2009 15:40:43, Ulrich Weigand wrote:
> Hello,
>
> this patch fixes gdbserver for the SPU target, which was quite broken
> since the recent multi-process merge. Many of the spu-low.c routines
> were not fully adapted to common code changes, so it didn't even
> compile ...
Argh, very sorry about it. Hmm, I was just noticing... Does this file
have any dependency on SPU specific headers? For the next time, can one
build this file with a regular ppc gcc?
> In addition, I've run into a bug in prepare_resume_reply:
> it wouldn't null-terminate the T packet on targets without thread
> support, causing GDB to receive garbage.
Thanks!
--
Pedro Alves
next prev parent reply other threads:[~2009-04-03 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 14:40 Ulrich Weigand
2009-04-03 14:47 ` Pedro Alves [this message]
2009-04-03 15:03 ` 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=200904031547.59755.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--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