kdb stack trace misses some frames.
Keith Owens
kaos at sgi.com
Mon Aug 25 00:10:48 PDT 2003
On Mon, 25 Aug 2003 15:44:35 +0900,
TeJun Huh <tejun at aratech.co.kr> wrote:
> While I was debugging 2.4.21 kernel with kdb v4.3, a cpu hit a
>deadlock but the stack trace had some problems.
Standard kdb commands for debugging i386 backtrace problems.
set LINES 10000
set BTSP 1
set KDBDEBUG 0x19
bt
Capture all the kdb output and send it to kaos at sgi.com, not to the
list. The detailed debugging will show why kdb is getting false
positives.
More information about the kdb
mailing list