From owner-freebsd-hackers Sat Apr 3 14: 8: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5A39215035 for ; Sat, 3 Apr 1999 14:07:57 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA05755; Sat, 3 Apr 1999 15:06:08 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA50844; Sat, 3 Apr 1999 15:06:27 -0700 (MST) Message-Id: <199904032206.PAA50844@harmony.village.org> To: Bob Bishop Subject: Re: Any way to... Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 03 Apr 1999 20:02:09 GMT." References: Date: Sat, 03 Apr 1999 15:06:27 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Bob Bishop writes: : >... get a kernel stack trace of a running process? : gdb -k /kernel /dev/mem, I expect How to I get that from gdb? gdb will tell me where in the kernel things are now, but not where a process may be sleeping or stuck. Actually, looking at the "top" output, shows that pppd is stuck in "select" state, so getting a kernel stack trace of that wouldn't be helpful. I don't know how ppp works in the kernel, but am trying to track down problems where it wedges our serial line and we have to kill pppd with SIGKILL in order for it to notice (SIGTERM and SIGHUP don't seem to produce any effect). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message