Skip to content

Commit fd2e455

Browse files
SinaKarvandigitbook-bot
authored andcommitted
GitBook: [#883] update 11
1 parent 236b9c3 commit fd2e455

File tree

8 files changed

+13
-13
lines changed

8 files changed

+13
-13
lines changed

commands/extension-commands/cpuid.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -104,15 +104,15 @@ Your custom code will be executed in vmx-root mode. Take a look at [this topic](
104104

105105
**Run Custom Code (Unconditional)**
106106

107-
Monitoring process id **0x490** for **CPUID** instruction execution and runs 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) for more information.
107+
Monitoring process id **0x490** for **CPUID** instruction execution and run 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) for more information.
108108

109109
```c
110110
HyperDbg> !cpuid pid 490 code {90 90 90}
111111
```
112112
113113
**Run Custom Code (Conditional)**
114114
115-
Monitoring process id **0x490** for **CPUID** instruction execution and runs 3 nops whenever the event condition is triggered and runs 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
115+
Monitoring process id **0x490** for **CPUID** instruction execution and run 3 nops whenever the event condition is triggered and runs 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
116116
117117
```c
118118
HyperDbg> !cpuid pid 490 code {90 90 90} condition {90 90 90}

commands/extension-commands/dr.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -106,15 +106,15 @@ Your custom code will be executed in vmx-root mode. Take a look at [this topic](
106106

107107
**Run Custom Code (Unconditional)**
108108

109-
Monitoring process ID **0x490** for any access to **hardware debug registers** and running 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) for more information.
109+
Monitoring process ID **0x490** for any access to **hardware debug registers** and run 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) for more information.
110110

111111
```c
112112
HyperDbg> !dr pid 490 code {90 90 90}
113113
```
114114
115115
**Run Custom Code (Conditional)**
116116
117-
Monitoring process ID **0x490** for any access to **hardware debug registers** and running 3 nops whenever the event condition is triggered and running 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
117+
Monitoring process ID **0x490** for any access to **hardware debug registers** and run 3 nops whenever the event condition is triggered and run 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
118118
119119
```c
120120
HyperDbg> !dr pid 490 code {90 90 90} condition {90 90 90}
@@ -128,7 +128,7 @@ Keep in mind that a conditional event can be used in **Breaking to Debugger** an
128128

129129
This command uses the same method to [send IOCTL for regular events](https://docs.hyperdbg.org/design/debugger-internals/ioctl-requests-for-events).
130130

131-
As **EventType** use `DEBUG_REGISTERS_ACCESSED` in **DEBUGGER_GENERAL_EVENT_DETAIL**.
131+
As **EventType** use `DEBUG_REGISTERS_ACCESSED` in `DEBUGGER_GENERAL_EVENT_DETAIL`.
132132

133133
### Design
134134

commands/extension-commands/interrupt.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ HyperDbg> !interrupt code {90 90 90}
116116
117117
**Run Custom Code (Conditional)**
118118
119-
Monitoring the external-interrupts occurrence and running 3 nops whenever the event condition is triggered and running 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
119+
Monitoring the external-interrupts occurrence and run 3 nops whenever the event condition is triggered and run 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
120120
121121
```c
122122
HyperDbg> !interrupt code {90 90 90} condition {90 90 90}

commands/extension-commands/monitor.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ Your custom code will be executed in vmx-root mode. Take a look at [this topic](
136136

137137
**Run Custom Code (Unconditional)**
138138

139-
Monitoring reads and writes on address from ``fffff800`4ed60000`` to ``fffff800`4ed60100`` and runs 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) for more information.
139+
Monitoring reads and writes on address from ``fffff800`4ed60000`` to ``fffff800`4ed60100`` and run 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) for more information.
140140

141141
```c
142142
HyperDbg> !monitor rw fffff800`4ed60000 fffff800`4ed60100 code {90 90 90}
@@ -158,7 +158,7 @@ Keep in mind that a conditional event can be used in **Breaking to Debugger** an
158158

159159
This command uses the same method to [send IOCTL for regular events](https://docs.hyperdbg.org/design/debugger-internals/ioctl-requests-for-events).
160160

161-
As **EventType** use `HIDDEN_HOOK_READ` in the case you want just reads, use `HIDDEN_HOOK_WRITE` in the case you want just writes and use `HIDDEN_HOOK_READ_AND_WRITE` in the case you want both reads and writes and send the start address (**from address**) of where you want to monitor in `OptionalParam1`and end address (**to address**) of where you want to monitor in `OptionalParam2`address **DEBUGGER_GENERAL_EVENT_DETAIL**.
161+
As **EventType** use `HIDDEN_HOOK_READ` in the case you want just reads, use `HIDDEN_HOOK_WRITE` in the case you want just writes and use `HIDDEN_HOOK_READ_AND_WRITE` in the case you want both reads and writes and send the start address (**from address**) of where you want to monitor in `OptionalParam1`and end address (**to address**) of where you want to monitor in `OptionalParam2`address `DEBUGGER_GENERAL_EVENT_DETAIL`.
162162

163163
### Design
164164

commands/extension-commands/pmc.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ HyperDbg> !pmc pid 490 code {90 90 90}
112112
113113
**Run Custom Code (Conditional)**
114114
115-
Monitoring process id **0x490** for **RDPMC** instruction execution and runs 3 nops whenever the event condition is triggered and runs 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
115+
Monitoring process id **0x490** for **RDPMC** instruction execution and run 3 nops whenever the event condition is triggered and runs 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
116116
117117
```c
118118
HyperDbg> !pmc pid 490 code {90 90 90} condition {90 90 90}

commands/extension-commands/syscall.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ HyperDbg> !syscall 55 pid 490 code {90 90 90}
126126
127127
**Run Custom Code (Conditional)**
128128
129-
Monitoring process id **0x490** for syscall-number **0x55** and runs 3 nops whenever the event condition is triggered and runs 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
129+
Monitoring process id **0x490** for syscall-number **0x55** and runs 3 nops whenever the event condition is triggered and run 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
130130
131131
```c
132132
HyperDbg> !syscall 55 pid 490 code {90 90 90} condition {90 90 90}

commands/extension-commands/tsc.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ HyperDbg> !tsc pid 490 code {90 90 90}
112112
113113
**Run Custom Code (Conditional)**
114114
115-
Monitoring process id **0x490** for **RDTSC/RDTSCP** instruction execution and runs 3 nops whenever the event condition is triggered and runs 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
115+
Monitoring process id **0x490** for **RDTSC/RDTSCP** instruction execution and run 3 nops whenever the event condition is triggered and runs 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
116116
117117
```c
118118
HyperDbg> !tsc pid 490 code {90 90 90} condition {90 90 90}

commands/extension-commands/vmcall.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -112,14 +112,14 @@ HyperDbg> !vmcall pid 490 code {90 90 90}
112112
113113
**Run Custom Code (Conditional)**
114114
115-
Monitoring process id **0x490** for **VMCALL** instruction execution and runs 3 nops whenever the event condition is triggered and runs 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
115+
Monitoring process id **0x490** for **VMCALL** instruction execution and run 3 nops whenever the event condition is triggered and runs 3 nops whenever the event is triggered. Take a look at [Run Custom Code](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action#run-custom-codes) and [how to create a condition](https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition) for more information.
116116
117117
```c
118118
HyperDbg> !vmcall pid 490 code {90 90 90} condition {90 90 90}
119119
```
120120

121121
{% hint style="success" %}
122-
Keep in mind that a conditional event can be used in **Breaking to Debugger** and **Running Script** too. _\*\*_
122+
Keep in mind that a conditional event can be used in **Breaking to Debugger** and **Running Script** too.
123123
{% endhint %}
124124

125125
### IOCTL

0 commit comments

Comments
 (0)