Lua:debug setBreakpoint - Revision history

TheyCallMeTim13: moved debug setBreakpoint to Lua:debug setBreakpoint

2018-01-25T00:17:06Z

moved debug setBreakpoint to Lua:debug setBreakpoint

TheyCallMeTim13 at 21:59, 19 March 2017

2017-03-19T21:59:14Z

TheyCallMeTim13 at 13:14, 19 March 2017

2017-03-19T13:14:26Z

Raijinili: creating page

2016-01-22T02:38:16Z

creating page

CecilLovins1: Created page with 'By employing this analysis, you can just as easily gain knowledge on what types of [http://www.loyalpest.com/Bed-Bug-Control/bed-bug-control.html Exterminator Richmond Va Bed Bug…'

2015-05-11T01:14:09Z

Created page with 'By employing this analysis, you can just as easily gain knowledge on what types of [http://www.loyalpest.com/Bed-Bug-Control/bed-bug-control.html Exterminator Richmond Va Bed Bug…'

New page

By employing this analysis, you can just as easily gain knowledge on what types of [http://www.loyalpest.com/Bed-Bug-Control/bed-bug-control.html Exterminator Richmond Va Bed Bugs] companies are currently operational within your specific part of the globe and the cost that they require.

← Older revision		Revision as of 21:59, 19 March 2017
Line 23:		Line 23:
	* function: function or string. A function or the name of a function to call when the breakpoint triggers.		* function: function or string. A function or the name of a function to call when the breakpoint triggers.
	</onlyinclude>		</onlyinclude>
		+
		+
		+	{{LuaSeeAlso}}

← Older revision		Revision as of 13:14, 19 March 2017
Line 1:		Line 1:
		+	[[Category:Lua]]
	<onlyinclude>		<onlyinclude>
	[[debug_setBreakpoint]](address[, size, trigger[, method]][, function])		[[debug_setBreakpoint]](address[, size, trigger[, method]][, function])

← Older revision		Revision as of 02:38, 22 January 2016
Line 1:		Line 1:
−	~~By employing this analysis~~, ~~you can just as easily gain knowledge~~ on ~~what~~ types of [~~http~~://~~www.loyalpest~~.com/~~Bed~~-~~Bug~~-~~Control~~/~~bed~~-~~bug~~-~~control~~.~~html Exterminator Richmond Va Bed Bugs~~] ~~companies are currently operational within your specific part~~ of the ~~globe and the cost that they require~~.	+	<onlyinclude>
		+	[[debug_setBreakpoint]](address[, size, trigger[, method]][, function])
		+
		+	Add a breakpoint at an address. Optional parameters are size, trigger, method, and function. Meaningful forms:
		+
		+	debug_setBreakpoint(address)
		+	debug_setBreakpoint(address, function)
		+	debug_setBreakpoint(address, size, trigger)
		+	debug_setBreakpoint(address, size, trigger, function)
		+	debug_setBreakpoint(address, size, trigger, method)
		+	debug_setBreakpoint(address, size, trigger, method, function)
		+
		+	* size: integer. Number of bytes to break for counting from the address. Ignored if trigger is "execute" (the default).
		+	* trigger: enum (integer). Type of access to break on. Default: bptExecute. Valid types are:[[https://github.com/cheat-engine/cheat-engine/blob/master/Cheat%20Engine/debuggertypedefinitions.pas#L37 debuggertypedefinitions.pas]]
		+	** bptExecute: break when the instruction pointer EIP is in the area
		+	** bptAccess: break when memory in the area is accessed
		+	** bptWrite: break when memory in the area is written to
		+	* method: enum (integer). How to implement the breakpoint. Default: Pascal variable preferedBreakpointMethod, set by ???. Valid methods are:[[https://github.com/cheat-engine/cheat-engine/blob/master/Cheat%20Engine/debuggertypedefinitions.pas#L30 debuggertypedefinitions.pas]]
		+	** bpmInt3: Interrupt? (Software breakpoint?)
		+	** bpmDebugRegister: ?? (Hardware breakpoint?)
		+	** bpmException: Exception?
		+	* function: function or string. A function or the name of a function to call when the breakpoint triggers.
		+	</onlyinclude>

← Older revision	Revision as of 00:17, 25 January 2018
(No difference)