Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <hui_zhu@mentor.com>
To: <gdb-patches@sourceware.org>
Cc: <lgustavo@codesourcery.com>, Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH] Support targets that know how to continue over breakpoints[1/4] -- GDB
Date: Tue, 12 Mar 2013 10:04:00 -0000	[thread overview]
Message-ID: <513EFD85.2090107@mentor.com> (raw)
In-Reply-To: <51322425.6090007@mentor.com>

Ping http://sourceware.org/ml/gdb-patches/2013-03/msg00054.html

Thanks,
Hui

On 03/03/13 00:09, Hui Zhu wrote:
> Hello,
>
> According to the mail thread in http://sourceware-org.1504.n7.nabble.com/PATCH-Support-targets-that-know-how-to-step-over-breakpoints-td61666.html
> I update patches to change step to continue.  When thread hop needed, GDB can use continue over breakpoints let the inferior keep going.
>
> The interface that add to target is:
> to_can_continue_over_breakpoints, it will return true if target can continue over breakpoints.
> to_next_continue_over_breakpoints, call this function before call to_resume will make to_resume do continue_over_breakpoints instead of continue.
>
> This patch is the GDB part that support continue over breakpoints.  And there also have patches for doc, server and test.  I will introduce them clear inside the mails of that paches.
>
> Please help me review it.
>
> Thanks,
> Hui
>
> 2013-03-03  Luis Machado  <lgustavo@codesourcery.com>
>          Pedro Alves  <pedro@codesourcery.com>
>          Hui Zhu  <hui_zhu@mentor.com>
>
>      * infrun.c (handle_inferior_event): Check if target can continue
>      over breakpoints.
>
>      * remote.c (struct remote_state): New member
>      can_continue_over_breakpoints.
>      (remote_continue_over_breakpoints_feature): New.
>      (remote_protocol_features): Add ContinueOverBreakpoints feature.
>      (remote_open_1): Clear can_continue_over_breakpoints.
>      (remote_is_cob): New.
>      (append_resumption, remote_resume): Check remote_is_cob.
>      (remote_can_continue_over_breakpoints,
>       remote_next_continue_over_breakpoints): New.
>      (init_remote_ops): Set remote_ops.to_can_continue_over_breakpoints
>      to remote_can_continue_over_breakpoints.
>      Set to_next_continue_over_breakpoints to
>      remote_next_continue_over_breakpoints.
>
>      * target.c (update_current_target): Inherit
>      to_can_continue_over_breakpoints, and default it to return 0.
>      Inherit to_next_continue_over_breakpoints.
>
>      * target.h (struct target_ops): Add new
>      to_can_step_over_breakpoints member.
>      (target_can_step_over_breakpoints): New.
>


  parent reply	other threads:[~2013-03-12 10:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-02 16:09 Hui Zhu
2013-03-02 16:11 ` [PATCH] Support targets that know how to continue over breakpoints[2/4] -- Doc Hui Zhu
2013-03-02 16:13   ` [PATCH] Support targets that know how to continue over breakpoints[3/4] -- gdbserver Hui Zhu
2013-03-02 16:14     ` [PATCH] Support targets that know how to continue over breakpoints[4/4] -- testsuite Hui Zhu
2013-03-03  2:18       ` Hui Zhu
2013-03-24 14:45         ` Hui Zhu
2013-05-07  2:46           ` Hui Zhu
2013-03-12 10:05       ` Hui Zhu
2013-03-02 16:20     ` [PATCH] Support targets that know how to continue over breakpoints[3/4] -- gdbserver Eli Zaretskii
2013-03-03  2:15       ` Hui Zhu
2013-03-24 14:10         ` Hui Zhu
2013-03-25  3:46           ` Eli Zaretskii
2013-03-25  8:06             ` Hui Zhu
2013-05-07  2:45           ` Hui Zhu
2013-03-12 10:05     ` Hui Zhu
2013-03-02 16:19   ` [PATCH] Support targets that know how to continue over breakpoints[2/4] -- Doc Eli Zaretskii
2013-03-03  2:06     ` Hui Zhu
2013-03-03  3:51       ` Eli Zaretskii
2013-03-03  3:58         ` Hui Zhu
2013-03-12 10:04   ` Hui Zhu
2013-05-07  2:37     ` Hui Zhu
2013-03-12 10:04 ` Hui Zhu [this message]
2013-03-24 12:33 ` [PATCH] Support targets that know how to continue over breakpoints[1/4] -- GDB Hui Zhu
2013-05-07  2: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=513EFD85.2090107@mentor.com \
    --to=hui_zhu@mentor.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    --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