From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 18 01:53:08 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A35ED37B425; Fri, 18 Jul 2003 01:53:08 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3A1543FBF; Fri, 18 Jul 2003 01:53:07 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfi0c.dialup.mindspring.com ([165.247.200.12] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19dQuK-0004SF-00; Fri, 18 Jul 2003 01:48:04 -0700 Message-ID: <3F17B3AE.1FD5CAC6@mindspring.com> Date: Fri, 18 Jul 2003 01:45:34 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20030715223653.Y36933-100000@mail.econolodgetulsa.com> <20030718080659.GA26490@garage.freebsd.pl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4b994b8dcdf21965064187efc94e447e3a8438e0f32a48e08350badd9bab72f9c350badd9bab72f9c cc: freebsd-hackers@freebsd.org cc: Robert Watson Subject: Re: running 5.1-RELEASE with no procfs mounted (lockups?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 08:53:09 -0000 Pawel Jakub Dawidek wrote: > +> truss Relies on the event model of procfs; there have been some > +> initial patches and discussion of migrating truss to ptrace() but > +> I don't think we have anything very usable yet. I'd be happy to > +> be corrected on this. :-) > > Hmm, why to change this behaviour? Is there any functionality that > ktrace(1) doesn't provide? It can interactively run in another window, giving you realtime updates on what's happening up to the point of a kernel crash. With ktrace, you are relatively screwed. Another good example is that it dump out information that ktrace can't, because of where it synchronizes. Some people recently have been seeing "EAGAIN" when they haven't expected it, with the process exiting immediately after that, with no real clue as to where in the code it's happening (e.g. which system call); truss will show this, if run in another terminal window, but ktrace will not (yes, I know it should; it doesn't. If you can't reconcile this with how you think ktrace should work, then fix it). -- Terry