Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] multi-executable support
Date: Wed, 21 Oct 2009 02:18:00 -0000	[thread overview]
Message-ID: <daef60380910201918v2053aae2m9fd0bb0a3709b04b@mail.gmail.com> (raw)
In-Reply-To: <200910201220.54860.pedro@codesourcery.com>

Thanks.

Hui

On Tue, Oct 20, 2009 at 19:20, Pedro Alves <pedro@codesourcery.com> wrote:
> On Tuesday 20 October 2009 07:13:58, Hui Zhu wrote:
>> darwin-nat.c
>>   if (breakpoint_inserted_here_p (pc))
>
> Thanks.  "grep breakpoint_inserted_here_p *nat*" doesn't find
> any other missing adjustment in native target files.  I've no easy way
> to test this, but the needed change is very simple.  Plus, this
> function is a copy of linux-nat.c:cancel_breakpoint, where I did
> the exact same change.
>
> I'm applying this.
>
> 2009-10-20  Pedro Alves  <pedro@codesourcery.com>
>
>        * darwin-nat.c (cancel_breakpoint): Pass the regcache's address
>        space to breakpoint_inserted_here_p.
>
> ---
>  gdb/darwin-nat.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: src/gdb/darwin-nat.c
> ===================================================================
> --- src.orig/gdb/darwin-nat.c   2009-10-20 12:15:12.000000000 +0100
> +++ src/gdb/darwin-nat.c        2009-10-20 12:16:03.000000000 +0100
> @@ -995,7 +995,7 @@ cancel_breakpoint (ptid_t ptid)
>   CORE_ADDR pc;
>
>   pc = regcache_read_pc (regcache) - gdbarch_decr_pc_after_break (gdbarch);
> -  if (breakpoint_inserted_here_p (pc))
> +  if (breakpoint_inserted_here_p (get_regcache_aspace (regcache), pc))
>     {
>       inferior_debug (4, "cancel_breakpoint for thread %x\n",
>                      ptid_get_tid (ptid));
>
>
> --
> Pedro Alves
>


  reply	other threads:[~2009-10-21  2:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200910191106.28905.pedro@codesourcery.com>
2009-10-20  6:14 ` Hui Zhu
2009-10-20 11:20   ` Pedro Alves
2009-10-21  2:18     ` Hui Zhu [this message]
2009-10-20 15:05 ` Ken Werner
2009-10-20 15:36   ` Pedro Alves
2009-10-20 15:54     ` Ken Werner
2009-10-20 16:34       ` Pedro Alves
2009-10-21  8:27 ` Obvious fix: deprecated_insert_raw_breakpoint change (was [commit] multi-executable support) Pierre Muller
2009-10-21  8:40   ` Pedro Alves
2009-11-13  1:09 ` [commit] multi-executable support Paul Pluzhnikov
2009-11-15 22:53   ` Pedro Alves
2009-11-16 18:42     ` Paul Pluzhnikov

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=daef60380910201918v2053aae2m9fd0bb0a3709b04b@mail.gmail.com \
    --to=teawater@gmail.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