generating an execution trace using adb?

generating an execution trace using adb?

Post by bugbe » Tue, 25 Mar 2003 20:00:45

I'm trying to generate a trace file of the execution
of my program. In particular I would like to generate
a stack trace whenever a particular function is called.

I *LIKE* trace files, because I can awk-grep-perl
in them, and extract useful information. I'd rather
do that that type endlessly into a de*)

I'd like to use adb because it's ubiqutous and reliable.
So I tried the following:

my_func:b $C ; :c
(i.e. set a break point on my_func, and when you hit
it, output a stack and, then continue).

it hits the break point, outputs a stack trace AND STOPS.

Can anyone help?



1. To get execution trace of a program

What is an easy way to get the execution trace for compiled code? This could
be as simple as inserting a "printf" statement at the beginning of each user
function & possibly a way to contain recursion. Is there a way to do this
using profiled code (gprof) or using a debugger?

Thanks in advance,

2. Block driver and /proc/partitions

3. Producing a trace of a program's execution?

4. Yggdrasil & Mach64 don't like each other!

5. To get execution trace ...

6. siig scsi pro pci on WIN98 problem

7. tracing csh execution to track down a "variable name too long error"

8. Animation in Konqueror

9. To get execution trace ...

10. Generating stack trace in interrupt handler

11. Generating a function call trace

12. Generating memory traces for Linux programs - how?

13. How to generate symbolic stack trace (possibly at runtime) ???