Date: Wed, 11 Apr 2007 15:02:28 -0700 From: Alfred Perlstein <alfred@freebsd.org> To: Ed Maste <ed.maste@gmail.com> 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: <20070411220228.GG2382@elvis.mu.org> In-Reply-To: <88607eb20704111346q5c463b60w2547084231a11227@mail.gmail.com> References: <200704100403.l3A43ZnL057659@repoman.freebsd.org> <88607eb20704101217x4e3c81f9xf914f7da7714daf8@mail.gmail.com> <20070411195935.GA2382@elvis.mu.org> <88607eb20704111346q5c463b60w2547084231a11227@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Ed Maste <ed.maste@gmail.com> [070411 13:46] wrote: > 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? 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070411220228.GG2382>