From: Hui Zhu <teawater@gmail.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Pedro Alves <pedro@codesourcery.com>,
Marc Khouzam <marc.khouzam@ericsson.com>,
Michael Snyder <msnyder@vmware.com>,
Thiago Jung Bauermann <bauerman@br.ibm.com>,
Eli Zaretskii <eliz@gnu.org>,
paawan1982@yahoo.com
Subject: [RFA] Submit process record and replay fourth time, 5/8
Date: Sat, 21 Mar 2009 16:03:00 -0000 [thread overview]
Message-ID: <daef60380903210902v31f4afe4o96678e89b1d16710@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
This patch to add some process record and replay to infrun.c.
Code for function "use_displaced_stepping" is make sure that displaced
stepping function will disable when process record and replay target
is opened. Because process record and replay target doesn't support
displaced stepping function.
Code for function "proceed" is call function "record_not_record_set"
to set process record and replay target doesn't record the execute
log. Because when GDB resume the inferior, process record and replay
target doesn't need to record the memory and register store operation
of GDB.
2009-03-21 Hui Zhu <teawater@gmail.com>
* infrun.c (use_displaced_stepping): Return false if process
record and replay target is used.
(proceed): Call function "record_not_record_set" if pocess
record and replay target is used.
2008-12-26 Michael Snyder <msnyder@vmware.com>
* infrun.c (proceed): Don't call record_not_record_set.
[-- Attachment #2: 5-infrun.txt --]
[-- Type: text/plain, Size: 1595 bytes --]
---
infrun.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
--- a/infrun.c
+++ b/infrun.c
@@ -49,6 +49,8 @@
#include "mi/mi-common.h"
#include "event-top.h"
+#include "record.h"
+
/* Prototypes for local functions */
static void signals_info (char *, int);
@@ -603,7 +605,8 @@ use_displaced_stepping (struct gdbarch *
return (((can_use_displaced_stepping == can_use_displaced_stepping_auto
&& non_stop)
|| can_use_displaced_stepping == can_use_displaced_stepping_on)
- && gdbarch_displaced_step_copy_insn_p (gdbarch));
+ && gdbarch_displaced_step_copy_insn_p (gdbarch)
+ && current_target.to_stratum != record_stratum);
}
/* Clean out any stray displaced stepping state. */
@@ -2108,6 +2111,10 @@ adjust_pc_after_break (struct execution_
if (software_breakpoint_inserted_here_p (breakpoint_pc)
|| (non_stop && moribund_breakpoint_here_p (breakpoint_pc)))
{
+ struct cleanup *old_cleanups = NULL;
+ if (current_target.to_stratum == record_stratum)
+ old_cleanups = record_gdb_operation_disable_set ();
+
/* When using hardware single-step, a SIGTRAP is reported for both
a completed single-step and a software breakpoint. Need to
differentiate between the two, as the latter needs adjusting
@@ -2131,6 +2138,9 @@ adjust_pc_after_break (struct execution_
|| !currently_stepping (ecs->event_thread)
|| ecs->event_thread->prev_pc == breakpoint_pc)
regcache_write_pc (regcache, breakpoint_pc);
+
+ if (current_target.to_stratum == record_stratum)
+ do_cleanups (old_cleanups);
}
}
next reply other threads:[~2009-03-21 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 16:03 Hui Zhu [this message]
2009-03-25 7:23 ` Hui Zhu
2009-04-15 17:04 ` Hui Zhu
2009-04-21 13:32 ` Pedro Alves
2009-04-22 9:09 ` Hui Zhu
2009-04-27 22:22 ` Pedro Alves
2009-04-28 10:03 ` 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=daef60380903210902v31f4afe4o96678e89b1d16710@mail.gmail.com \
--to=teawater@gmail.com \
--cc=bauerman@br.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=msnyder@vmware.com \
--cc=paawan1982@yahoo.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