Messages in this thread | | | Date | Wed, 7 Mar 2001 22:55:48 +0100 (CET) | From | Urban Widmark <> | Subject | Re: Q. about oops backtrace |
| |
On Wed, 7 Mar 2001, Pete Zaitcev wrote:
> Trace; c0127414 <handle_mm_fault+114/1a0> > Trace; c0136a2d <kunmap_high+7d/90> > Trace; c012722e <do_anonymous_page+de/110> > Trace; c0127290 <do_no_page+30/a0> > Trace; c0127414 <handle_mm_fault+114/1a0> > Trace; c014cdec <dput+1c/170> > Trace; c0143f80 <cached_lookup+10/50> > Trace; c0144aae <path_walk+85e/940> > Trace; c014cdec <dput+1c/170> > Trace; c01392c9 <chrdev_open+59/a0> > Trace; c0138130 <dentry_open+c0/150> > Trace; c013805d <filp_open+4d/60> > Trace; c0148b97 <sys_ioctl+247/2a0> > Trace; c01091c7 <system_call+33/38> > > What is with those recursive handle_mm_fault calls?
Unless I'm mistaken the call trace in an i386 oops is printed by arch/i386/kernel/traps.c:show_trace()
And it simply prints any value within certain limits. if (((addr >= (unsigned long) &_stext) && (addr <= (unsigned long) &_etext)) || ((addr >= module_start) && (addr <= module_end))) { /* ... print it ... */
If a function is passed as a parameter it will of course be on the stack, even when it isn't a return value.
The dput entries are strange too, does dput call path_walk? (is the translation from numbers to symbols correct?)
/Urban
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |