Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: aristovski@qnx.com (Aleksandar Ristovski)
Cc: pedro@codesourcery.com (Pedro Alves),
	brobecker@adacore.com,        gdb-patches@sourceware.org
Subject: Re: [rfc v2][rft (procfs, nto-procfs)] Fix signal bypass heuristic with software single-step
Date: Tue, 26 Apr 2011 17:34:00 -0000	[thread overview]
Message-ID: <201104261734.p3QHYR33002293@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <1302053790.16582.71.camel@qnxws7629> from "Aleksandar Ristovski" at Apr 05, 2011 09:36:30 PM

Aleksandar Ristovski wrote:

> I tested your patch on self-hosted x86 Neutrino and it did not show any 
> regressions.

Great!  Thanks for your support.

> BTW, can you incorporate this in your patch to remove compile issues:
> 
> @@ -72,9 +72,11 @@ static ptid_t do_attach (ptid_t ptid);
> 
>   static int procfs_can_use_hw_breakpoint (int, int, int);
> 
> -static int procfs_insert_hw_watchpoint (CORE_ADDR addr, int len, int type);
> +static int procfs_insert_hw_watchpoint (CORE_ADDR addr, int len, int type,
> +                                       struct expression *);
> 
> -static int procfs_remove_hw_watchpoint (CORE_ADDR addr, int len, int type);
> +static int procfs_remove_hw_watchpoint (CORE_ADDR addr, int len, int type,
> +                                       struct expression *);
> 
>   static int procfs_stopped_by_watchpoint (void);

Sure; I've checked this part in right away.

Thanks,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  parent reply	other threads:[~2011-04-26 17:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19  1:54 [rfc][rft " Ulrich Weigand
2011-03-22 17:25 ` Pedro Alves
2011-03-24 16:39   ` Ulrich Weigand
2011-03-31 19:42   ` [rfc v2][rft " Ulrich Weigand
2011-04-04  9:47     ` Pedro Alves
2011-04-05 19:22       ` Ulrich Weigand
2011-04-05 19:33         ` Aleksandar Ristovski
2011-04-05 22:56           ` Ulrich Weigand
2011-04-06  1:37             ` Aleksandar Ristovski
2011-04-06 17:00               ` Ulrich Weigand
2011-04-26 17:34               ` Ulrich Weigand [this message]
2011-04-06  6:07         ` Joel Brobecker
2011-04-06 17:01           ` Ulrich Weigand
2011-04-27  1:12         ` Joel Brobecker
2011-04-27 13:31           ` Ulrich Weigand
2011-03-22 17:37 ` [rfc][rft " 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=201104261734.p3QHYR33002293@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=aristovski@qnx.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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