Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 0/1] Threaded Watchpoints
Date: Mon, 10 Sep 2007 18:30:00 -0000	[thread overview]
Message-ID: <20070910183037.GB18690@caradoc.them.org> (raw)
In-Reply-To: <1189446990.4318.21.camel@localhost>

On Mon, Sep 10, 2007 at 02:56:30PM -0300, Luis Machado wrote:
> As for the testcases, since PPC only supports one hardware watchpoint
> per process, we should work that test case in a different way or mark it
> as unsupported for PPC and write a different test case.

Oops, you're correct.  This should be easy to check for in the
testcase; I don't remember if we'll get an error or a software
watchpoint for the second watchpoint.  Actually, I think PPC will
currently "succeed" and things will go wrong...

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-09-10 18:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13 13:51 Luis Machado
2007-08-20 17:33 ` Luis Machado
2007-08-20 17:40   ` Luis Machado
2007-09-05  2:04     ` Daniel Jacobowitz
2007-09-05 12:31       ` Luis Machado
2007-09-10  0:21         ` Daniel Jacobowitz
2007-09-10 15:34           ` Luis Machado
2007-09-10 15:44             ` Daniel Jacobowitz
2007-09-10 17:56               ` Luis Machado
2007-09-10 18:30                 ` Daniel Jacobowitz [this message]
2007-09-10 18:23           ` Ulrich Weigand
2007-09-10 18:29             ` Daniel Jacobowitz
2007-09-10 18:44               ` Ulrich Weigand
2007-09-10 18:54                 ` Daniel Jacobowitz
2007-09-10 19:03                   ` Ulrich Weigand
2007-09-10 19:12                     ` Daniel Jacobowitz
2007-09-10 19:31                     ` Mark Kettenis

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=20070910183037.GB18690@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.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