Re: problems with call-graph in version 0.9

[John L. <le...@mo...>]

On Thu, Jul 21, 2005 at 01:23:34AM -0400, Shanshan Ding wrote:

> sudo opstack -c quake2

You mean opreport -c quake2

(It's always best if you exactly cut and paste what you typed).

> The output is not desirable: 
> 
> CPU: CPU with timer interrupt, speed 0 MHz (estimated)
> Profiling through timer interrupt

Hmm, the timer interrupt is supposed to pick up the ->backtrace setting.
Maybe that code doesn't work.

You didn't give your CPU type or kernel version? Why is oprofile in
timer mode?

> By the way, I got rid of the "-fomit-frame-pointer" compiling options
> in quake2 so that oprofile can make use of the frame pointer.  And
> also my kernel was compiled with frame pointer support(actually, since
> I not profiling kernel, only applications I don't have to enable this
> with kernel, do I? )

That's right.

regards
john