From owner-freebsd-hackers Fri Sep 15 9: 7:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.mobilix.dk (mail.mobilix.dk [194.234.53.85]) by hub.freebsd.org (Postfix) with ESMTP id 92F0337B440 for ; Fri, 15 Sep 2000 09:07:16 -0700 (PDT) Received: from lflat.vas.mobilix.dk (gw-vas.mobilix.net [212.97.206.4]) by mail.mobilix.dk (8.8.7/8.8.7) with ESMTP id OAA20016 for ; Fri, 15 Sep 2000 14:55:00 +0200 Received: by lflat.vas.mobilix.dk (Postfix, from userid 72044) id 1000CA820; Fri, 15 Sep 2000 14:25:44 +0200 (CEST) Date: Fri, 15 Sep 2000 14:25:44 +0200 From: Vadim Belman To: freebsd-hackers@freebsd.org Subject: Live debugging of a process being hung in a syscall. Message-ID: <20000915142543.A3697@lflat.vas.mobilix.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seem like I got a NFS-related bug here where a httpd process hung in a uninterruptable wait (a disk operation, most likely). In order to locate the problem I need the process' stack trace first. gdb doesn't attach to the process for obvious reasons. Making a crashdump doesn't inspire me at all. The question is: is there a way of working with /proc entries? I.e. is it possible to get all what I need from, say, /proc//mem? -- /Voland Vadim Belman E-mail: voland@lflat.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message