summaryrefslogtreecommitdiff
path: root/src/base/remote_gdb.hh
diff options
context:
space:
mode:
authorGabe Black <gabeblack@google.com>2014-12-05 22:37:03 -0800
committerGabe Black <gabeblack@google.com>2014-12-05 22:37:03 -0800
commit4a8a0a07982b7896127d0cb723fde08b3825bb48 (patch)
tree32274c02ae9dca6d6ebad156e559c9afcc44cabb /src/base/remote_gdb.hh
parentfb07d43b1a4a903fb2e51b41685eb5814d9f9e11 (diff)
downloadgem5-4a8a0a07982b7896127d0cb723fde08b3825bb48.tar.xz
misc: Generalize GDB single stepping.
The new single stepping implementation for x86 doesn't rely on any ISA specific properties or functionality. This change pulls out the per ISA implementation of those functions and promotes the X86 implementation to the base class. One drawback of that implementation is that the CPU might stop on an instruction twice if it's affected by both breakpoints and single stepping. While that might be a little surprising, it's harmless and would only happen under somewhat unlikely circumstances.
Diffstat (limited to 'src/base/remote_gdb.hh')
-rw-r--r--src/base/remote_gdb.hh18
1 files changed, 16 insertions, 2 deletions
diff --git a/src/base/remote_gdb.hh b/src/base/remote_gdb.hh
index 62f98f29a..6cca485e3 100644
--- a/src/base/remote_gdb.hh
+++ b/src/base/remote_gdb.hh
@@ -209,11 +209,25 @@ class BaseRemoteGDB
}
protected:
+ class SingleStepEvent : public Event
+ {
+ protected:
+ BaseRemoteGDB *gdb;
+
+ public:
+ SingleStepEvent(BaseRemoteGDB *g) : gdb(g)
+ {}
+
+ void process();
+ };
+
+ SingleStepEvent singleStepEvent;
+
virtual void getregs() = 0;
virtual void setregs() = 0;
- virtual void clearSingleStep() = 0;
- virtual void setSingleStep() = 0;
+ void clearSingleStep();
+ void setSingleStep();
PCEventQueue *getPcEventQueue();
EventQueue *getComInstEventQueue();