Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>,
	 "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [PATCH, ppc] Fix hw *points for embedded ppc in a threaded environment
Date: Tue, 07 May 2013 07:44:00 -0000	[thread overview]
Message-ID: <5188B0DD.3000905@codesourcery.com> (raw)
In-Reply-To: <5178C3A6.7010302@codesourcery.com>

On 04/25/2013 07:48 AM, Luis Machado wrote:
> gdb/
> 2013-04-25  Luis Machado<lgustavo@codesourcery.com>
>
> 	* ppc-linux-nat.c (ppc_linux_new_thread): Clear the new thread's
> 	debug state prior to replicating existing hardware watchpoints or
> 	breakpoints.
>
> gdb/testsuite/
> 2013-04-25  Luis Machado<lgustavo@codesourcery.com>
>
> 	* gdb.threads/wp-replication.c: New file.
> 	* gdb.threads/wp-replication.exp: New file.

I've checked this in now.


  reply	other threads:[~2013-05-07  7:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 20:33 Luis Machado
2013-04-18  0:19 ` Sergio Durigan Junior
2013-04-18  0:51   ` Luis Machado
2013-04-22 21:09 ` Luis Machado
2013-04-22 21:09   ` Pedro Alves
2013-04-23  0:05     ` Pedro Alves
2013-04-23  1:15       ` Pedro Alves
2013-04-23 20:25         ` Luis Machado
2013-04-23 23:18         ` Luis Machado
2013-04-24  3:19           ` Pedro Alves
2013-04-24  6:28             ` Luis Machado
2013-04-24 19:04               ` Pedro Alves
2013-04-25 14:13                 ` Luis Machado
2013-05-07  7:44                   ` Luis Machado [this message]
2013-04-24  4:36           ` Pedro Alves
  -- strict thread matches above, loose matches on Subject: below --
2012-08-06 14:33 Luis Gustavo
2012-08-06 18:40 ` Jan Kratochvil
2012-08-06 19:02   ` Luis Gustavo
2012-08-06 20:28     ` Jan Kratochvil
2012-08-07 14:55       ` Luis Gustavo
2012-08-07 15:00         ` Jan Kratochvil
2012-08-07 15:02           ` Luis Gustavo
2012-12-27 19:50 ` Luis Machado
2013-01-22 12:12   ` Pedro Alves

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=5188B0DD.3000905@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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