📚 OpenRCE is preserved as a read-only archive. Launched at RECon Montreal in 2005. Registration and posting are disabled.








Flag: Tornado! Hurricane!

 Forums >>  Debuggers  >>  Hit trace with Ollydbg

Topic created on: July 30, 2006 13:00 CDT by suszter .

Could anybody help me how can I use Hit trace when I switch to another memory page.

Example:

I load notepad.exe to Olly, then I open Memory map window to switch to another address now comdlg32. After I've switched and clicked View in disassembly Hit trace clear out of Menu. Why?

Thanks!

  anonymouse     July 31, 2006 10:55.33 CDT
thats the beauty of context sensitive menus :) it wont let you do what is not possible

file -> open -> notepad

since by default you already have
auto start analysis of main module checked
ollydbg automatically analyses notepad so hit trace is available

now you land in comdlg via either
alt+m (view memory)-> text section -> view in disassembler
or
alt+e (view executable file) -> follow entry

it is yet unanalysed so you have to analyse it first

hit ctrl+a

or if you prefer to have all the modules thats loaded analysed in one go

alt+e -> analyse all modules

now hit trace will be available on every modules

configure what you want to hit trace and have fun

  suszter     July 31, 2006 12:58.38 CDT
> alt+m (view memory)-> text section -> view in disassembler

Does work, but If I get data section, then I load address to disasm window. Ctrl+A does not work. Analyse code and Remove analysis from module menus are not in context. My data section has executable code.

  anonymouse     July 31, 2006 13:53.37 CDT
Does work, but If I get data section, then I load address to disasm window. Ctrl+A does not work. Analyse code and Remove analysis from module menus are not in context. My data section has executable code.

you can try joe_stewerts analysethis_plugin that available
here for download

its data section and contains executable code ?
you mean its data section only by its name and not by charecteristics ?

some times dumping the whole memory as one single section as code make analysis look better

  suszter     July 31, 2006 14:25.35 CDT
> you can try joe_stewerts analysethis_plugin that as code make analysis look better

"EIP is outside the range of a known executable module" That was the problem, still is OK. Hit trace does work after Analyse This plugin. Thaks for you and Joe.

Note: Registration is required to post to the forums.

There are 31,328 total registered users.


Recently Created Topics
[help] Unpacking VMP...
Mar/12
Reverse Engineering ...
Jul/06
let 'IDAPython' impo...
Sep/24
set 'IDAPython' as t...
Sep/24
GuessType return une...
Sep/20
About retrieving the...
Sep/07
How to find specific...
Aug/15
How to get data depe...
Jul/07
Identify RVA data in...
May/06
Question about memor...
Dec/12


Recent Forum Posts
Finding the procedur...
rolEYder
Question about debbu...
rolEYder
Identify RVA data in...
sohlow
let 'IDAPython' impo...
sohlow
How to find specific...
hackgreti
Problem with ollydbg
sh3dow
How can I write olly...
sh3dow
New LoadMAP plugin v...
mefisto...
Intel pin in loaded ...
djnemo
OOP_RE tool available?
Bl4ckm4n


Recent Blog Entries
halsten
Mar/14
Breaking IonCUBE VM

oleavr
Oct/24
Anatomy of a code tracer

hasherezade
Sep/24
IAT Patcher - new tool for ...

oleavr
Aug/27
CryptoShark: code tracer ba...

oleavr
Jun/25
Build a debugger in 5 minutes

More ...


Recent Blog Comments
nieo on:
Mar/22
IAT Patcher - new tool for ...

djnemo on:
Nov/17
Kernel debugger vs user mod...

acel on:
Nov/14
Kernel debugger vs user mod...

pedram on:
Dec/21
frida.github.io: scriptable...

capadleman on:
Jun/19
Using NtCreateThreadEx for ...

More ...


Imagery
SoySauce Blueprint
Jun 6, 2008

[+] expand

View Gallery (11) / Submit