On Fri, 27 Aug 2004 14:21:45 -0500, Timur Tabi <[EMAIL PROTECTED]> wrote: >I'm new to kdb, so I'm sure this is a misunderstanding on my part, but >when I use the bt command to display a stack trace, I get this: > >[1]kdb> bt >Stack traceback for pid 18117 >0xf5864220 18117 18102 1 1 R 0xf58644b0 *cconfig >EBP EIP Function (args) >0xec7d9f6c 0xf8afdb02 [ccil]ccilioctl+0x562 (0x0, 0xf5875b80, 0x0, 0xf5875b80, 0x0) > ccil 0xf8afd5a0 0xf8afe0d0 >0xec7d9ef4 0xc0173844 chrdev_open+0xd4 (0xbffff130, 0xec7d9f90, 0xf7867d1c, >0xf5875b80, 0xc01670c7) > kernel 0xc0173770 0xc0173930 >0xec7d9fbc 0xc017da96 sys_ioctl+0x2d6 > kernel 0xc017d7c0 0xc017dc6c > 0xc01091a9 sysenter_past_esp+0x52 > kernel 0xc0109157 0xc01091d0 > >The problem is that the function ccilioctl() has only four parameters, >not five:
man linux/Documentation/kdb/kdb_bt.man - "The bt command may print more arguments for a function ..." >int ccilioctl(struct inode * inode, struct file *f, volatile unsigned >int cmd, unsigned long arg) > >What does "(0x0, 0xf5875b80, 0x0, 0xf5875b80, 0x0)" mean? I seriously >doubt this is the parameter list for ccilioctl, even with the extra >number, because none of the four parameters are zero. It is possible for kdb to get the backtrace and arguments wrong, especially if the kernel is compiled without frame pointers. See kdb_bt.man. --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
