stack trace changes

[Martin Hunt]

On Thu, 2006-10-12 at 15:18 -0700, Mike Mason wrote:

> I tested print_backtrace on 2.6.17-1.2187_FC5 on x86_64. I now see a 
> single line(as before) followed by "Inexact backtrace:" and then 
> nothing. 

Are you using the example from 3050?

probe kernel.function("schedule@kernel/sched.c") {
        print_backtrace();
}

On RHEL4 (2.6.9-42.0.3.ELsmp), I get

0xffffffff80309677 : schedule+0x15/0xb6f []
Inexact backtrace:
 0xffffffff8010e7f4 : cpu_idle+0x32/0x34 []
 0xffffffff804eb67b : start_kernel+0x1d6/0x1da []
 0xffffffff804eb1d5 : _sinittext+0x1d5/0x1d7 []

0xffffffff80309677 : schedule+0x15/0xb6f []
Inexact backtrace:
 0xffffffff8013575f : autoremove_wake_function+0x9/0x2e []
 0xffffffff80133dfe : __wake_up_common+0x43/0x63 []
 0xffffffff80147795 : worker_thread+0xe2/0x22a []
 0xffffffff80133dad : default_wake_function+0x0/0xe []
 0xffffffff80133dad : default_wake_function+0x0/0xe []
 0xffffffff8014b4f4 : keventd_create_kthread+0x0/0x48 []
 0xffffffff801476b3 : worker_thread+0x0/0x22a []
 0xffffffff8014b4f4 : keventd_create_kthread+0x0/0x48 []
 0xffffffff8014b4cb : kthread+0xc8/0xf1 []
 0xffffffff80110f47 : child_rip+0x8/0x11 []
 0xffffffff8014b4f4 : keventd_create_kthread+0x0/0x48 []
 0xffffffff8014b403 : kthread+0x0/0xf1 []
 0xffffffff80110f3f : child_rip+0x0/0x11 []

0xffffffff80309677 : schedule+0x15/0xb6f []
Inexact backtrace:
 0xffffffff8010e7f4 : cpu_idle+0x32/0x34 []
[...]

I don't have FC5 installed on x86_64, but I tried FC6 with the 
new unwinder disabled and it worked just like it did with the 
old 2.6.9 kernel.

So it should work.