If a process was waiting on a lock and the lock code was in a module
then kdb bt gave incorrect results. This patch handles locks in
modules as well as built in.
However there is another problem, btp (not bt) gives incorrect results
if the specified process was running when kdb was invoked. The cause
is known (incorrect assumptions about thread.e[is]p) but the best fix
has not been determined. In the meantime, take btp output with a pinch
of salt, use mds <stack_address> if in doubt.
Modid: 2.4.0-test1-xfs:slinx:64420a
Date: Thu Jun 15 21:00:40 PDT 2000
Workarea:
kao1.melbourne.sgi.com:/hosts/sherman/home/kaos/isms/slinx/2.4.0-test1-xfs
Author: kaos
The following file(s) were checked into:
bonnie.engr.sgi.com:/isms/slinx/2.4.0-test1-xfs
linux/arch/i386/kdb/kdba_bt.c - 1.5
http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.4-xfs/linux/arch/i386/kdb/kdba_bt.c.diff?r1=text&tr1=1.5&r2=text&tr2=1.4&f=h
linux/arch/i386/vmlinux.lds - 1.8
http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.4-xfs/linux/arch/i386/vmlinux.lds.diff?r1=text&tr1=1.8&r2=text&tr2=1.7&f=h
|