[Crash-utility] about stack frame

mo can faicker.mo at gmail.com
Sat Mar 2 09:54:21 UTC 2013


Hi,
This is part of a stack backtrace of kernel 2.6.32-279.19.1.el6.x86_64,
bt -f
...
#7 [ffff880028283b38] dev_queue_xmit at ffffffff8142dac9
   ffff880028283b40: ffff880028283b80 ffffffff81445ffa 
   ffff880028283b50: ffff8801175ef020 ffff880079551680 
   ffff880028283b60: ffff880116a07480 000000000000000e 
   ffff880028283b70: ffff880116a074c0 ffff88007a266c80 
   ffff880028283b80: ffff880028283bd0 ffffffff81432b75 
#8 [ffff880028283b88] neigh_resolve_output at ffffffff81432b75
   ffff880028283b90: ffff880028283c10 ffffffff814547b4 
   ffff880028283ba0: ffffffff81464e50 00000000000055b8 
   ffff880028283bb0: ffff880037a7a800 000000000000000e 
   ffff880028283bc0: ffff880079551680 ffff880037a7a858 
   ffff880028283bd0: ffff880028283c10 ffffffff81464f8c 
...
crash> whatis dev_queue_xmit
int dev_queue_xmit(struct sk_buff *);

Take a look at #7, I know the value "ffffffff81432b75" is the return address, the saved RBP is ffff880028283bd0. What about the values between the address ffff880028283bd0 and address ffff880028283bd0? Are they stack variables in function dev_queue_xmit? How can I distinguish compared the source code? Actually, I want to display the variables(including function parameters and local variables).
Thanks.





More information about the Crash-utility mailing list