From: Hui Zhu <teawater@gmail.com>
To: gdb-patches ml <gdb-patches@sourceware.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [RFA] patch for [Bug gdb/11253]
Date: Mon, 08 Mar 2010 02:35:00 -0000 [thread overview]
Message-ID: <daef60381003071834i7250f743m7a648621c7dacba8@mail.gmail.com> (raw)
In-Reply-To: <20100228183805.GA23351@host0.dyn.jankratochvil.net>
Could some people help us review this patch?
Thanks,
Hui
On Mon, Mar 1, 2010 at 02:38, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> On Fri, 26 Feb 2010 04:25:58 +0100, Hui Zhu wrote:
>> This patch is for bug 11253 http://sourceware.org/bugzilla/show_bug.cgi?id=11253
>
> just extended it a bit but it remains the same.
>
> No regressions on {x86_64,x86_64-m32,i686}-fedora12-linux-gnu.
>
> since
> Re: [RFA] Fix hw watchpoints in process record.
> From: Pedro Alves <pedro at codesourcery dot com>
> http://sourceware.org/ml/gdb-patches/2009-11/msg00476.html
> http://sourceware.org/ml/gdb-cvs/2009-11/msg00187.html
> commit 1ab0b876af2e2410fa462e901623669f29d75c89
>
> there are IMO missing the resets in record_open.
>
>
> Thanks,
> Jan
>
>
> 2010-02-28 Jan Kratochvil <jan.kratochvil@redhat.com>
> Hui Zhu <teawater@gmail.com>
>
> * record.c (record_open_1): Check tmp_to_stopped_by_watchpoint and
> tmp_to_stopped_data_address.
> (record_open): Reset tmp_to_stopped_by_watchpoint and
> tmp_to_stopped_data_address.
> * target.c (init_dummy_target): Add to_stopped_by_watchpoint and
> to_stopped_data_address.
>
> --- a/gdb/record.c
> +++ b/gdb/record.c
> @@ -867,6 +867,10 @@ record_open_1 (char *name, int from_tty)
> error (_("Could not find 'to_insert_breakpoint' method on the target stack."));
> if (!tmp_to_remove_breakpoint)
> error (_("Could not find 'to_remove_breakpoint' method on the target stack."));
> + if (!tmp_to_stopped_by_watchpoint)
> + error (_("Could not find 'to_stopped_by_watchpoint' method on the target stack."));
> + if (!tmp_to_stopped_data_address)
> + error (_("Could not find 'to_stopped_data_address' method on the target stack."));
>
> push_target (&record_ops);
> }
> @@ -897,6 +901,8 @@ record_open (char *name, int from_tty)
> tmp_to_xfer_partial = NULL;
> tmp_to_insert_breakpoint = NULL;
> tmp_to_remove_breakpoint = NULL;
> + tmp_to_stopped_by_watchpoint = NULL;
> + tmp_to_stopped_data_address = NULL;
>
> /* Set the beneath function pointers. */
> for (t = current_target.beneath; t != NULL; t = t->beneath)
> --- a/gdb/target.c
> +++ b/gdb/target.c
> @@ -2838,6 +2838,9 @@ init_dummy_target (void)
> dummy_target.to_has_stack = (int (*) (struct target_ops *)) return_zero;
> dummy_target.to_has_registers = (int (*) (struct target_ops *)) return_zero;
> dummy_target.to_has_execution = (int (*) (struct target_ops *)) return_zero;
> + dummy_target.to_stopped_by_watchpoint = return_zero;
> + dummy_target.to_stopped_data_address =
> + (int (*) (struct target_ops *, CORE_ADDR *)) return_zero;
> dummy_target.to_magic = OPS_MAGIC;
> }
>
>
next prev parent reply other threads:[~2010-03-08 2:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 3:26 Hui Zhu
2010-02-26 12:53 ` Jan Kratochvil
2010-02-28 15:38 ` Hui Zhu
2010-02-28 18:10 ` Jan Kratochvil
2010-02-28 18:38 ` Jan Kratochvil
2010-03-08 2:35 ` Hui Zhu [this message]
2010-03-08 4:39 ` Joel Brobecker
2010-03-08 13:35 ` Hui Zhu
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=daef60381003071834i7250f743m7a648621c7dacba8@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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