Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: "Pedro Alves" <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	 	"Michael Snyder" <msnyder@vmware.com>
Subject: [RFA] target adjust pc after break with itself
Date: Sun, 02 Nov 2008 06:02:00 -0000	[thread overview]
Message-ID: <daef60380811012301g336aee73w274ff053a07f48a6@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

Hi Pedro,

According to your idea, I write a patch
"target_adjust_pc_with_itself.txt" for it. It's for the main trunk and
20080930 branch.

2008-11-02  Hui Zhu  <teawater@gmail.com>

	* target.h (target_ops): Add "to_adjust_pc_with_itself".
	Return true if target adjust pc after break with itself.
	(target_adjust_pc_with_itself): New macro.
	Call "to_adjust_pc_with_itself".
	* target.c (update_current_target): Set
	"to_adjust_pc_with_itself".
	* infrun.c (adjust_pc_after_break): If
	"target_adjust_pc_with_itself" return true, not adjust pc.

To make P record support it. I make another patch
"record_adjust_pc_with_itself.txt".

2008-11-02  Hui Zhu  <teawater@gmail.com>

	* record.c (record_adjust_pc_with_itself): New function.
	Return true.
	(init_record_ops): Set to_adjust_pc_with_itself point to
	record_adjust_pc_with_itself.

Thanks,
Hui

[-- Attachment #2: target_adjust_pc_with_itself.txt --]
[-- Type: text/plain, Size: 1692 bytes --]

--- a/target.h
+++ b/target.h
@@ -536,6 +536,9 @@ struct target_ops
     /* Can target execute in reverse?  */
     int (*to_can_execute_reverse) ();
 
+    /* Can target adjust pc after break with itself?  */
+    int (*to_adjust_pc_with_itself) (ptid_t ptid);
+
     /* Does this target support debugging multiple processes
        simultaneously?  */
     int (*to_supports_multi_process) (void);
@@ -1155,6 +1158,11 @@ extern int target_stopped_data_address_p
      (current_target.to_can_execute_reverse ? \
       current_target.to_can_execute_reverse () : 0)
 
+/* Can target adjust pc after break with itself?  */
+#define target_adjust_pc_with_itself(ptid) \
+     (current_target.to_adjust_pc_with_itself ? \
+      current_target.to_adjust_pc_with_itself (ptid) : 0)
+
 extern const struct target_desc *target_read_description (struct target_ops *);
 
 #define target_get_ada_task_ptid(lwp, tid) \
--- a/target.c
+++ b/target.c
@@ -468,6 +468,7 @@ update_current_target (void)
       INHERIT (to_make_corefile_notes, t);
       INHERIT (to_get_thread_local_address, t);
       INHERIT (to_can_execute_reverse, t);
+      INHERIT (to_adjust_pc_with_itself, t);
       /* Do not inherit to_read_description.  */
       INHERIT (to_get_ada_task_ptid, t);
       /* Do not inherit to_search_memory.  */
--- a/infrun.c
+++ b/infrun.c
@@ -1944,6 +1944,9 @@ adjust_pc_after_break (struct execution_
      target with both of these set in GDB history, and it seems unlikely to be
      correct, so gdbarch_have_nonsteppable_watchpoint is not checked here.  */
 
+  if (target_adjust_pc_with_itself (ecs->ptid))
+    return;
+
   if (ecs->ws.kind != TARGET_WAITKIND_STOPPED)
     return;
 

[-- Attachment #3: record_adjust_pc_with_itself.txt --]
[-- Type: text/plain, Size: 609 bytes --]

--- a/record.c
+++ b/record.c
@@ -954,6 +954,12 @@ record_can_execute_reverse (void)
   return 1;
 }
 
+static int
+record_adjust_pc_with_itself (ptid_t ptid)
+{
+  return 1;
+}
+
 static void
 init_record_ops (void)
 {
@@ -975,6 +981,7 @@ init_record_ops (void)
   record_ops.to_insert_breakpoint = record_insert_breakpoint;
   record_ops.to_remove_breakpoint = record_remove_breakpoint;
   record_ops.to_can_execute_reverse = record_can_execute_reverse;
+  record_ops.to_adjust_pc_with_itself = record_adjust_pc_with_itself;
   record_ops.to_stratum = record_stratum;
   record_ops.to_magic = OPS_MAGIC;
 }

             reply	other threads:[~2008-11-02  6:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-02  6:02 teawater [this message]
2008-11-04  0:15 ` teawater
2008-11-04 18:32 ` Pedro Alves
2008-11-05  1:39   ` teawater
2008-11-05  4:57     ` teawater

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=daef60380811012301g336aee73w274ff053a07f48a6@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --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