This adds new example to the ``String Formatting'' page.
It obvious that to dereference a register with Intel syntax, one should
use [eax] syntax. But when I had tried that for first time I messed
something and got "Formatting error". I then tried AT&T syntax, C
syntax, I even wrote a message to the Telegram group... Therefore, I
believe such example would be helpful for someone like me.
Signed-off-by: Ruslan Garipov <[email protected]>
@@ -4,7 +4,7 @@ Attempt to download a symbol from a Symbol Store.
## arguments
`[arg1]` Module name (with or without extension) to attept to download symbols for. When not specified, an attempt will be done to download symbols for all loaded modules.
`[arg1]` Module name (with or without extension) to attempt to download symbols for. When not specified, an attempt will be done to download symbols for all loaded modules.
`[arg2]` Symbol Store URL. When not specified, thedefault store will be used.
Delete an exception breakpoint set using the SetExceptionBPX command.
## arguments
`[arg1]` Name, exception name or code of the exception breakpoint to delete. If this argument is not specified, all exception breakpoints will be deleted.
Disable an exception breakpoint set using the SetExceptionBPX command.
## arguments
`[arg1]` Name, exception name or code of the exception breakpoint to enable. If this argument is not specified, all exception breakpoints will be disabled.
Enable an exception breakpoint set using the SetExceptionBPX command.
## arguments
`[arg1]` Name, exception name or code of the exception breakpoint to enable. If this argument is not specified, all exception breakpoints will be enabled.
Set an INT3 (SHORT/LONG)or UD2 breakpoint and optionally assign a name to it.
## arguments
`arg1` Address to put a breakpoint on. This can be an API name[not implemented].
`arg1` Address to put a breakpoint on. This can be an API name.
`[arg2]` Name of the breakpoint, use quotation marks to include spaces. This name can be used by the EnableBPX, DisableBPX and DeleteBPX functions as alias, but is mainly intended to provide a single line of information about the currently-hit breakpoint. When arg2 equals to a valid type (arg3) the type is used and arg2 is ignored.
Set an exception breakpoint. If an exception breakpoint is active, all the exceptions with the same chance and code will be captured as a breakpoint event and will not be handled by the default exception handling policy.
## arguments
`arg1` Exception name or code of the new exception breakpoint
`[arg2]` Chance. Set to `first`/`1` to capture first-chance exceptions, `second`/`2` to capture second-chance exceptions, `all`/`3` to capture all exceptions. Default value is `first`.
@@ -6,9 +6,9 @@ Set a memory breakpoint (GUARD_PAGE) on the whole memory region the provided add
`arg1` Addressof or inside a memory region that will be watched.
`[arg2]` 1/0 restore the memory breakpoint once it's hit? When this value is not equal to one, it's assumed to be arg3. This means "bpm eax,r" would be the same command as: "bpm eax,0,r".
`[arg2]` 1/0 restore the memory breakpoint once it's hit? When this value is not equal to '1' or '0', it's assumed to be arg3. This means "bpm eax,r" would be the same command as: "bpm eax,0,r".
`[arg3]` Breakpoint type, it can be 'r' (execute+read),'w' (write) or 'x' (execute). Per default, it's a combination of execute, read and write.
`[arg3]` Breakpoint type, it can be 'a' (read+write+execute) 'r' (read),'w' (write) or 'x' (execute). Per default, it's 'a' (read+write+execute)
Set a memory breakpoint (GUARD_PAGE) on a specific memory range.
## arguments
`start` Start of the memory range.
`size` Size of the memory range.
`[type]` Breakpoint type, it can be 'a' (read+write+execute) 'r' (read),'w' (write) or 'x' (execute). Per default, it's 'a' (read+write+execute). Append `ss` for a singleshot breakpoint (you can also use [`SetMemoryBreakpointSingleshoot`](../conditional-breakpoint-control/SetMemoryBreakpointSingleshoot.md) to do this).
Sets the command to execute when an exception breakpoint is hit. If the command condition is not specified, it will be executed when the debugger breaks, otherwise it will be executed when the condition is satisfied.
## arguments
`arg1` The name, exception name or code of the exception breakpoint.
Sets the command condition of an exception breakpoint. When command condition is not specified, the command will be executed when the debugger would break, otherwise it will be executed when the condition is satisfied.
## arguments
`arg1` The name, exception name or code of the exception breakpoint.
`[arg2]` The command condition (default condition when not specified).
Sets the exception breakpoint condition. When this condition is set, it is evaluated every time the exception occurs (chance must match) and the debugger would stop only if condition is not 0.
## arguments
`arg1` The name, exception name or code of the exception breakpoint.
Sets the fast resume flag of an exception breakpoint. If this flag is set and the break condition doesn't evaluate to break, no GUI, plugin, logging or any other action will be performed, except for incrementing the hit counter.
## arguments
`arg1` The name, exception name or code of the exception breakpoint.
`[arg2]` The fast resume flag. If it is 0 (default), fast resume is disabled, otherwise it is enabled
Sets log text when an exception breakpoint is hit. When log condition is not specified, it will always be logged regardless of the break condition, otherwise it will be logged when the logging condition is satisfied.
## arguments
`arg1` The name, exception name or code of the exception breakpoint.
`[arg2]` The log format string (see introduction/formatting).
Sets the logging condition of an exception breakpoint. When log condition is not specified, log text always be logged regardless of the break condition, otherwise it will be logged when the logging condition is satisfied.
## arguments
`arg1` The name, exception name or code of the exception breakpoint.
`[arg2]` The logging condition (default condition when not specified).
Sets the command to execute when a librarian breakpoint is hit. If the command condition is not specified, it will be executed when the debugger breaks, otherwise it will be executed when the condition is satisfied.
Sets the command condition of a librarian breakpoint. When command condition is not specified, the command will be executed when the debugger would break, otherwise it will be executed when the condition is satisfied.
## arguments
`arg1` The DLL name.
`[arg2]` The command condition (default condition when not specified).
Sets the librarian breakpoint condition. When this condition is set, it is evaluated every time the breakpoint occurs and the debugger would stop only if condition is not 0.
Sets the fast resume flag of a librarian breakpoint. If this flag is set and the break condition doesn't evaluate to break, no GUI, plugin, logging or any other action will be performed, except for incrementing the hit counter.
## arguments
`arg1` The DLL name.
`[arg2]` The fast resume flag. If it is 0 (default), fast resume is disabled, otherwise it is enabled
Sets log text when a librarian breakpoint is hit. When log condition is not specified, it will always be logged regardless of the break condition, otherwise it will be logged when the logging condition is satisfied.
## arguments
`arg1` The DLL name.
`[arg2]` The log format string (see introduction/formatting).
Sets the logging condition of a librarian breakpoint. When log condition is not specified, log text always be logged regardless of the break condition, otherwise it will be logged when the logging condition is satisfied.
## arguments
`arg1` The DLL name.
`[arg2]` The logging condition (default condition when not specified).
Loaded 100 of 796 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.