Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ken Werner <ken@linux.vnet.ibm.com>
To: pmuldoon@redhat.com
Cc: gdb-patches@sourceware.org, Pedro Alves <pedro@codesourcery.com>,
	       Tom Tromey <tromey@redhat.com>,
	dan@codesourcery.com, eliz@gnu.org
Subject: Re: [patch] Add visible flag to breakpoints.
Date: Fri, 12 Nov 2010 12:43:00 -0000	[thread overview]
Message-ID: <201011121343.27553.ken@linux.vnet.ibm.com> (raw)
In-Reply-To: <m3pqucsza2.fsf@redhat.com>

[-- Attachment #1: Type: Text/Plain, Size: 276 bytes --]

On Thursday, November 11, 2010 3:36:21 pm Phil Muldoon wrote:
> So committed, thanks

This change introduces a small typo in the spu-tdep.c file which prevents the 
gdb from compiling if --target=spu is enabled. The attached patch fixes this 
issue. Ok to apply?

Regards
Ken

[-- Attachment #2: typo.patch --]
[-- Type: text/x-patch, Size: 660 bytes --]

ChangeLog:

2010-11-12  Ken Werner  <ken.werner@de.ibm.com>

	* spu-tdep.c (spu_catch_start): Fix typo.


Index: gdb/spu-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/spu-tdep.c,v
retrieving revision 1.63
diff -p -u -r1.63 spu-tdep.c
--- gdb/spu-tdep.c	11 Nov 2010 14:11:52 -0000	1.63
+++ gdb/spu-tdep.c	12 Nov 2010 12:37:49 -0000
@@ -1896,7 +1896,7 @@ spu_catch_start (struct objfile *objfile
 		     0 /* ignore_count */,
 		     AUTO_BOOLEAN_FALSE /* pending_break_support */,
 		     NULL /* ops */, 0 /* from_tty */, 1 /* enabled */,
-		     0 /* internal  */););
+		     0 /* internal  */);
 }
 
 

  reply	other threads:[~2010-11-12 12:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 16:28 Phil Muldoon
2010-09-30 16:41 ` Daniel Jacobowitz
2010-09-30 17:51   ` Phil Muldoon
2010-09-30 17:55     ` Pedro Alves
2010-09-30 18:12       ` Phil Muldoon
2010-10-08 12:51       ` Phil Muldoon
2010-10-08 13:35         ` Pedro Alves
2010-10-08 14:04           ` Phil Muldoon
2010-10-08 18:44             ` Tom Tromey
2010-10-12 20:25               ` Phil Muldoon
2010-10-12 21:34                 ` Tom Tromey
2010-10-13 12:45                   ` Phil Muldoon
2010-10-13 13:06                     ` Phil Muldoon
2010-10-13 15:36                     ` Tom Tromey
2010-10-16 18:42                     ` Pedro Alves
2010-10-16 19:03             ` Pedro Alves
2010-10-18 16:09               ` Tom Tromey
2010-10-22 21:05                 ` Phil Muldoon
2010-10-22 21:31                   ` Eli Zaretskii
2010-10-22 21:37                     ` Phil Muldoon
2010-10-23  9:07                       ` Eli Zaretskii
2010-10-31 21:07                   ` Pedro Alves
2010-11-11 14:36                     ` Phil Muldoon
2010-11-12 12:43                       ` Ken Werner [this message]
2010-11-12 12:49                         ` Pedro Alves
2010-11-12 12:58                           ` Ken Werner
2010-10-08 18:40         ` Tom Tromey
2010-09-30 17:04 ` Pedro Alves
2010-09-30 17:55   ` Phil Muldoon
2010-09-30 17:51 ` Eli Zaretskii
2010-10-05 22:28 ` Tom Tromey

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=201011121343.27553.ken@linux.vnet.ibm.com \
    --to=ken@linux.vnet.ibm.com \
    --cc=dan@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=pmuldoon@redhat.com \
    --cc=tromey@redhat.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