Generating a function call trace
Is it possible to arbitrarily generate (in a module say) a function call trace?
Simon Turvey
Quoted 4 lines · Simon Turvey
Is it possible to arbitrarily generate (in a module say) a function call trace?
Just insert the dereference of a NULL pointer where you wan't to have it.
The oops gives you what you wan't....
Or better attach the gdb to /proc/kmem (you will have to compile the kernel with
debugging on in front of this action) and have fun.
Quoted 6 lines · Martin Dalecki
Quoted 4 lines · Simon Turvey
Is it possible to arbitrarily generate (in a module say) a function call trace?
Quoted 6 lines
Just insert the dereference of a NULL pointer where you wan't to have it.
The oops gives you what you wan't....
Or better attach the gdb to/proc/kmem(you will have to compile the kernel with
debugging on in front of this action) and have fun.
I'm using this ia32-only solution, as killing userspace program is not acceptable under some conditions. Patch below was generated from my 2.5.0-pre1 tree.
Petr Vandrovec [email protected]
arch/i386/kernel/traps.c +36 -0
@@ -237,6 +237,42 @@printk ("\n" ); } +void printstate (void ) { + asmvolatile ( +"pushl %%ss\n\t" +"pushl %%esp\n\t" +"pushfl\n\t" +"pushl %%cs\n\t" +"call 1f\n" +"1:\n\t" +"pushl %%eax\n\t" +"pushl %%ds\n\t" +"pushl %%es\n\t" +"pushl %%eax\n\t" +"pushl %%ebp\n\t" +"pushl %%edi\n\t" +"pushl %%esi\n\t" +"pushl %%edx\n\t" +"pushl %%ecx\n\t" +"pushl %%ebx\n\t" +"movl %%esp,%%eax\n\t" +"pushl %%eax\n\t" +"call show_registers\n\t" +"addl $4,%%esp\n\t" +"popl %%ebx\n\t" +"popl %%ecx\n\t" +"popl %%edx\n\t" +"popl %%esi\n\t" +"popl %%edi\n\t" +"popl %%ebp\n\t" +"popl %%eax\n\t" +"popl %%es\n\t" +"popl %%ds\n\t" +"popl %%eax\n\t" +"addl $20,%%esp\n\t" + : : :"memory" ); +} +spinlock_t die_lock =SPIN_LOCK_UNLOCKED ;void die (const char * str,struct pt_regs * regs,long err)
kernel/ksyms.c +3 -0
@@ -71,6 +71,9 @@ };#endif +extern void printstate (void ); + +EXPORT_SYMBOL (printstate);EXPORT_SYMBOL (inter_module_register);EXPORT_SYMBOL (inter_module_unregister);
Quoted 2 lines · Simon Turvey
Is it possible to arbitrarily generate (in a module say) a function call trace?
gcc has builtin macros to trace back or ( on x86 ) you can simply chain through %esp/%ebp
- Davide
Quoted 8 lines · Davide Libenzi
Quoted 2 lines · Simon Turvey
Is it possible to arbitrarily generate (in a module say) a function call trace?
gcc has builtin macros to trace back or ( on x86 ) you can simply chain through %esp/%ebp
That only works if you compile with frame pointers, which the kernel turns off for performance reasons (due to register pressure on the x86).
--
Brian Gerst
Quoted 4 lines · Brian Gerst
Quoted 3 lines · Davide Libenzi
On Fri, 30 Nov 2001, Simon Turvey wrote:
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Is it possible to arbitrarily generate (in a module say) a function call trace?
gcc has builtin macros to trace back or ( on x86 ) you can simply chain through %esp/%ebp
That only works if you compile with frame pointers, which the kernel turns off for performance reasons (due to register pressure on the x86).
I thought it was a general question not a kernel code one. Sure -fomit-frame-pointer is on inside the kernel.
- Davide
Quoted 10 lines · Davide Libenzi
Quoted 7 lines · Brian Gerst
Quoted 6 lines · Davide Libenzi
Quoted 2 lines · Simon Turvey
Is it possible to arbitrarily generate (in a module say) a function call trace?
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
gcc has builtin macros to trace back or ( on x86 ) you can simply chain through %esp/%ebp
That only works if you compile with frame pointers, which the kernel turns off for performance reasons (due to register pressure on the x86).
I thought it was a general question not a kernel code one. Sure -fomit-frame-pointer is on inside the kernel.
With the , well exception, of the scheduler, which does the task switching by
overwriting his own return address on the stack by the address of the next jump point in a process, and needs the frame
pointer therefore ;-).
Try using 'lcrash', part of the LKCD project:
I'm not sure what you mean by arbitrarily (meaning, it could be at a snapshot point in time, or it could be while it is running, etc.) E-mail me if you have further questions, I'll try to help.
--Matt
Quoted 17 lines · Brian Gerst
Quoted 8 lines · Davide Libenzi
Quoted 2 lines · Simon Turvey
Is it possible to arbitrarily generate (in a module say) a function call trace?
gcc has builtin macros to trace back or ( on x86 ) you can simply chain through %esp/%ebp
That only works if you compile with frame pointers, which the kernel turns off for performance reasons (due to register pressure on the x86).
--
Brian Gerst