Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] [7/9] Cell multi-arch: Add "set spu stop-on-load" command
Date: Wed, 22 Jul 2009 19:05:00 -0000	[thread overview]
Message-ID: <83skgo4m5k.fsf@gnu.org> (raw)
In-Reply-To: <200907221717.n6MHHCgk014568@d12av02.megacenter.de.ibm.com>

> Date: Wed, 22 Jul 2009 19:17:12 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
> 
> Index: src/gdb/doc/gdb.texinfo
> ===================================================================
> --- src.orig/gdb/doc/gdb.texinfo
> +++ src/gdb/doc/gdb.texinfo
> @@ -17490,6 +17490,23 @@ and local store addresses and transfer s
>  
>  @end table
>   
> +When @value{GDBN} is debugging a combined PowerPC/SPU application
> +on the Cell Broadband Engine, it provides in addition the following
> +special commands:
> +
> +@table @code
> +@item set spu stop-on-load @var{arg}
> +@kindex set spu
> +Set whether to stop for new SPE threads.  When set to @code{on}, @value{GDBN}
> +will give control to the user when a new SPE thread enters its @code{main}
> +function.  The default is @code{off}.
> +
> +@item show spu stop-on-load
> +@kindex show spu
> +Show whether to stop for new SPE threads.
> +
> +@end table
> +
>  @node PowerPC
>  @subsection PowerPC
>  @cindex PowerPC architecture
> Index: src/gdb/NEWS
> ===================================================================
> --- src.orig/gdb/NEWS
> +++ src/gdb/NEWS
> @@ -254,6 +254,10 @@ kill inferior NUM
>  
>  * New options
>  
> +set spu stop-on-load
> +show spu stop-on-load
> +  Control whether to stop for new SPE threads during Cell/B.E. debugging.
> +
>  set sh calling-convention
>  show sh calling-convention
>    Control the calling convention used when calling SH target functions.

These parts are OK.

Thanks.


      reply	other threads:[~2009-07-22 18:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 17:18 Ulrich Weigand
2009-07-22 19:05 ` Eli Zaretskii [this message]

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=83skgo4m5k.fsf@gnu.org \
    --to=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