Date: Fri, 31 Aug 2007 15:03:18 -0700 From: "David O'Brien" <obrien@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-arch@freebsd.org Subject: Re: file locking. Message-ID: <20070831220318.GA4861@dragon.NUXI.org> In-Reply-To: <200708161635.20935.jhb@freebsd.org> References: <20070815233852.X568@10.0.0.1> <200708161056.31494.jhb@freebsd.org> <20070816131327.J568@10.0.0.1> <200708161635.20935.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 16, 2007 at 04:35:20PM -0400, John Baldwin wrote: > On Thursday 16 August 2007 04:18:51 pm Jeff Roberson wrote: > > Do we have an official stance on libkvm? Now that we have sysctl for > > run-time it's only useful for crashdump debugging. Really in most cases > > it could be replaced with a reasonable set of gcc scripts. > > s/gcc/gdb/. At work we do mostly post-mortem analysis, so having working > libkvm is still very important for us. xref the way I just fixed netstat to > work again on coredumps recently. Breaking fstat on coredumps would probably > be very annoying. This applies at Juniper as well. I think post-mortem analysis is a Big Deal(tm) to those developing commercial products based on FreeBSD. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070831220318.GA4861>