Tracing back a function

[Corthezz]

Hey there,
I want to trace back a function call a few levels. Previously it was always enough to set a breakpoint, wait for it to trigger and manually check return addresses pushed to the stack til the point where I want.
Now I got another function which is called multiple times a second and maybe one of 50 calls is relevant for me. In conclusion its more than annoying checking the registers / stack every time the breakpoint is hit.

Solving this one was easy by conditional logging (noting down registers if code is executed) and later on pausing the program with a conditional breakpoint whenever I need to.
Granting I got the program paused at my conditional bp is there any better way to trace back the program multiple calls beside analysing the stack manually?

Thanks in advance

[namreeb]

What debugger are you using? If it is either Visual Studio or Ollydbg, it will tell you the call stack. You don't have to do it manually.

[Corthezz]

What debugger are you using? If it is either Visual Studio or Ollydbg, it will tell you the call stack. You don't have to do it manually.

OllyDbg (filler).
Did some search and came up with this: http://stackoverflow.com/a/24195841

To clarify: I dont want to find all xrefs to a function but rather the function calls which finally lead to my bp being triggered. I know how to obtain return addresses but I am wondering if there is something like a call trace (In Visual Studio you can for example see the last few calls of the thread which hit the bp - need the same for Olly).

Also quite useful in this case: http://www.woodmann.com/forum/archiv...p/t-11550.html

[TOM_RUS]

Pretty sure ollydbg has callstack window at View -> Call stack.

[lolp1]

Pretty sure ollydbg has callstack window at View -> Call stack.

It does.

[Corthezz]

Well from time to time I enjoy creating useless threads
Thanks for the info.