Date: Wed, 11 Apr 2007 16:46:18 -0400 From: "Ed Maste" <ed.maste@gmail.com> To: "Alfred Perlstein" <alfred@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, Xin LI <delphij@freebsd.org>, 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 Message-ID: <88607eb20704111346q5c463b60w2547084231a11227@mail.gmail.com> In-Reply-To: <20070411195935.GA2382@elvis.mu.org> References: <200704100403.l3A43ZnL057659@repoman.freebsd.org> <88607eb20704101217x4e3c81f9xf914f7da7714daf8@mail.gmail.com> <20070411195935.GA2382@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/04/07, Alfred Perlstein <alfred@freebsd.org> wrote: > * Ed Maste <ed.maste@gmail.com> [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? -ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?88607eb20704111346q5c463b60w2547084231a11227>