Trees | Indices | Help |
---|
|
Breakpoints in Vtrace are platform independant objects that use the underlying trace objects to get things like the program counter and the break instruction. As long as platfforms are completely implemented, all breakpoint objects should be portable.
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|
|||
bpcodeobj =
|
|
Actually store off and replace memory for this process. This is caried out by the trace object itself when it begins running or stops. You probably never need to call this (see isEnabled() setEnabled() for boolean enable/disablle) |
Repair the process for continued execution. this does NOT make a breakpoint *inactive*, but removes it's "0xcc" from mem (see isEnabled() setEnabled() for boolean enable/dissable) |
This will return the address for this breakpoint. If the return'd address is None, this is a deferred breakpoint which needs to have resolveAddress() called to attempt to set the address. |
A callback to do housekeeping at the time the breakpoint is added to the tracer object. This should be used instead of activate for initialization time infoz to save on time per activate call... |
Breakpoints may also extend and implement "notify" which will be called whenever they are hit. If you want to continue the ability for this breakpoint to have bpcode, you must call this method from your override. |
Try to resolve the address for this break. If this is a statically addressed break, just return the address. If it has an "expression" use that to resolve the address... |
Use this method to set custom python code to run when this breakpoint gets hit. The code will have the following objects mapped into it's namespace when run: trace - the tracer vtrace - the vtrace module bp - the breakpoint |
Trees | Indices | Help |
---|
Generated by Epydoc 3.0.1 on Fri Nov 16 18:22:13 2012 | http://epydoc.sourceforge.net |