Re: Stack traces

From: Pat O'Rourke (orourke@mclinux.com)
Date: Thu Aug 10 2000 - 15:39:20 EST


> > How do others go about solving such problems? The only debugger I've found
> > for 2.2.12 kernels that would fit the bill is SGI's kgdb, and there's
> > obviously a bit of overhead involved in setting up the serial debugger.
>
> kdb (no 'g') from SGI can do the same without a serial line. Then it is
> as simple as btp <pid>

You can also use our (Mission Critical Linux's) crash command, assuming
you're on a supported platform (i386, alpha and ppc). For example,
to get a stack trace of netscape:

crash> ps | grep netscape
    835 673 1 c4298000 IN 13.7 29792 17896 netscape-commun
    837 835 0 c2ff8000 IN 0.2 16840 324 netscape-commun
crash> bt 835
PID: 835 TASK: c4298000 CPU: 1 COMMAND: "netscape-commun"
 #0 [c4299e34] schedule at c0115dfd
    (void)
 #1 [c4299edc] schedule_timeout at c01156af
    (13)
 #2 [c4299f18] do_select at c013eaff
    (13, c4299f68, c4299f64)
 #3 [c4299f80] sys_select at c013f03a
    (13, 50011e68, 0, 50011d68, 50011d50)
 #4 [c4299fbc] old_select at c010e1b1
    (50011c50)
 #5 [50011c48] system_call at c01090d7
    EAX: 00000052 EBX: 50011c50 ECX: 08db8c68 EDX: 50011e68
    DS: 002b ESI: bfffe744 ES: 002b EDI: 08c0ebdc
    SS: 002b ESP: 50011c44 EBP: 50011c48
    CS: 0023 EIP: 0891f91a ERR: 00000052 EFLAGS: 00000206
crash>

Pat

-- 
Patrick O'Rourke
orourke@missioncriticallinux.com

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Tue Aug 15 2000 - 21:00:22 EST