From owner-cvs-all@FreeBSD.ORG Wed Apr 11 22:02:21 2007 Return-Path: X-Original-To: cvs-all@freebsd.org Delivered-To: cvs-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E5BF16A405; Wed, 11 Apr 2007 22:02:21 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 7C26313C45A; Wed, 11 Apr 2007 22:02:21 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id A7A3C1A4D9D; Wed, 11 Apr 2007 15:02:28 -0700 (PDT) Date: Wed, 11 Apr 2007 15:02:28 -0700 From: Alfred Perlstein To: Ed Maste Message-ID: <20070411220228.GG2382@elvis.mu.org> References: <200704100403.l3A43ZnL057659@repoman.freebsd.org> <88607eb20704101217x4e3c81f9xf914f7da7714daf8@mail.gmail.com> <20070411195935.GA2382@elvis.mu.org> <88607eb20704111346q5c463b60w2547084231a11227@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <88607eb20704111346q5c463b60w2547084231a11227@mail.gmail.com> User-Agent: Mutt/1.4.2.2i Cc: cvs-src@freebsd.org, src-committers@freebsd.org, Xin LI , cvs-all@freebsd.org Subject: Re: cvs commit: src/usr.bin/truss Makefile amd64-fbsd.c extern.h i386-fbsd.c i386-linux.c ia64-fbsd.c main.c powerpc-fbsd.c setup.c sparc64-fbsd.c syscall.h syscalls.c truss.1 truss.h X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2007 22:02:21 -0000 * Ed Maste [070411 13:46] wrote: > On 11/04/07, Alfred Perlstein wrote: > >* Ed Maste [070410 12:47] wrote: > >> This would make the -s option to gcore redundant (since the process > >> will be stopped after attaching anyway). I don't know how useful a > >> core from a non-stopped process is, anyhow. > > > >Very, very useful. > > > >Imagine a running program that's having some form of abnormal > >behavior but can't be stopped (for long) or allowed to core... > > It's stopped for only as long as the core takes to be written. > > Currently, without the -s option the core produced by gcore is > inconsistent, and it's that behaviour that would be eliminated with my > change. Do you actually have a use for inconsistent core files? Not so much as a need for an inconsistent core so much as a need for a core without halting the program for the time it takes to dump core. -- - Alfred Perlstein