Date: Mon, 14 Aug 1995 16:40:40 +1000 From: Bruce Evans <bde@zeta.org.au> To: fn@pain.csrv.uidaho.edu, j@uriah.heep.sax.de Cc: current@freebsd.org Subject: Re: procfs problems in -current? Message-ID: <199508140640.QAA23880@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>...
>#10 0xf01a4423 in trap (frame={tf_es = -260374512, tf_ds = 16, tf_edi = 0,
> tf_esi = -260316288, tf_ebp = -272630680, tf_isp = -272630748,
> tf_ebx = 0, tf_edx = -260316172, tf_ecx = -260278528, tf_eax = 0,
> tf_trapno = 12, tf_err = -260374528, tf_eip = -260297713,
> tf_cs = -272695288, tf_eflags = 66118, tf_esp = -260316288,
> tf_ss = -260864512}) at ../../i386/i386/trap.c:299
>#11 0xf019a821 in calltrap ()
>#12 0xf07c4f4a in end ()
>#13 0xf0127678 in lookup (ndp=0xefbffe50) at ../../kern/vfs_lookup.c:490
>#14 0xf012704e in namei (ndp=0xefbffe50) at ../../kern/vfs_lookup.c:147
>...
>Frames #11 and #12 both displayed bogusly as ``end ()'' in DDB.
Unbogusly?
>This should be the exact trap location. I think the ``end + ...''
>means it has been executing code from the data/bss instead of the text
>segment.
It probably means that lkm code from the heap was being executed. It's
hard to debug such code, so I never use lkms :-).
Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508140640.QAA23880>