View Full Version : Call Bp
Jo_ti
September 5th, 2009, 11:49
Hi,
I know very well how to put bp on all intramodular calls but i want to put the bp over each and every call including intramodular calls.
Is it possible to have bp over all the call in code section??
HOW?
BanMe
September 5th, 2009, 12:19
OllyBOnE..might be something to look at...
Break On Execution..
D-Jester
September 5th, 2009, 12:32
Quote:
[Originally Posted by Jo_ti;82817]Hi,
I know very well how to put bp on all intramodular calls but i want to put the bp over each and every call including intramodular calls.
Is it possible to have bp over all the call in code section??
HOW? |
If all else fails, you can always set a memory "break on access" to a particular section
Jo_ti
September 5th, 2009, 13:23
Its not possible to put bp over all calls, jmps, mov commands ?. Any plugin or any other way. Basically i wan to trace compares so just want to put the bp over all the call after reaching at specific point. Because i am at a point where i know that something will call to the right routine. So just want to trace routine and dont want to miss that call which will call to that routine.
bunion
September 5th, 2009, 16:15
Jo-ti ive never used this option but olly has a trace function ..where u choose a call to strt tracing from and it records all subsequent calls and jumps and saves to file so you can go through it all noting register changes calls used etc etc ..sounds handy bro
from website
This debugging technique is basically very simple. Code is executed step by step, and debugger protocols every command, together with registers and flags, in the large circular buffer. When exception occurs, one can backtrace several (or hundreds of thousands) last commands and analyse conditions that led to error.
OllyDbg 1.06 has significantly improved the possibilities of run trace. Run trace shows modified registers and keeps important messages and operands of known functions. One can set conditions to pause run trace, profile traced code, write run trace to disk in order to overcome memory limitations or to compare two runs, debug self-modified programs, find ount when command at certain location was executed for the last time, and so on.
more info and trace tutorial
http://www.ollydbg.de/Tut_rtr.htm
is that what u want?
bunion
disavowed
September 5th, 2009, 22:20
Process Stalker (http://pedram.redhive.com/code/process_stalker) can be used for this purpose.
Powered by vBulletin® Version 4.2.2 Copyright © 2018 vBulletin Solutions, Inc. All rights reserved.