Displaying 2 results from an estimated 2 matches for "c0405f30".
2007 Apr 18
1
[PATCH] lguest32 kallsyms backtrace of guest.
...I did on lguest64.
When killing a guest, we read the guest stack to do a nice back trace of
the guest and send it via printk to the host.
So instead of just getting an error message from the lguest launcher of:
lguest: bad read address 537012178 len 1
I also get in my dmesg:
called from [<c0405f30>] show_trace_log_lvl+0x1a/0x2f
[<c04069aa>] show_trace+0x12/0x14
[<c0406a03>] dump_stack+0x16/0x18
[<f8c746de>] lguest_dump_lg_regs+0x22/0x13c [lg]
[<f8c7131b>] lgread+0x59/0x90 [lg]
[<f8c715bd>] run_guest+0x26b/0x406 [lg]
[<f8c739be>] read+0x73/0x7d [lg...
2007 Apr 18
1
[PATCH] lguest32 kallsyms backtrace of guest.
...I did on lguest64.
When killing a guest, we read the guest stack to do a nice back trace of
the guest and send it via printk to the host.
So instead of just getting an error message from the lguest launcher of:
lguest: bad read address 537012178 len 1
I also get in my dmesg:
called from [<c0405f30>] show_trace_log_lvl+0x1a/0x2f
[<c04069aa>] show_trace+0x12/0x14
[<c0406a03>] dump_stack+0x16/0x18
[<f8c746de>] lguest_dump_lg_regs+0x22/0x13c [lg]
[<f8c7131b>] lgread+0x59/0x90 [lg]
[<f8c715bd>] run_guest+0x26b/0x406 [lg]
[<f8c739be>] read+0x73/0x7d [lg...