From owner-freebsd-current Sat Nov 23 7:21:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D4CC37B401 for ; Sat, 23 Nov 2002 07:21:37 -0800 (PST) Received: from espresso.q9media.com (espresso.q9media.com [65.39.129.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB02443E91 for ; Sat, 23 Nov 2002 07:21:36 -0800 (PST) (envelope-from mike@espresso.q9media.com) Received: by espresso.q9media.com (Postfix, from userid 1002) id B79879BC3; Sat, 23 Nov 2002 10:12:18 -0500 (EST) Date: Sat, 23 Nov 2002 10:12:18 -0500 From: Mike Barcroft To: Nate Lawson Cc: Brad Knowles , current@FreeBSD.org Subject: Re: Searching for users of netncp and nwfs to help debug 5.0 problems Message-ID: <20021123101218.A99548@espresso.q9media.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from nate@root.org on Fri, Nov 22, 2002 at 10:19:20PM -0800 Organization: The FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Nate Lawson writes: > On Sat, 23 Nov 2002, Brad Knowles wrote: > > At 2:31 PM -0800 2002/11/22, Terry Lambert wrote: > > > > > A "bug-filing wizard" would be useful. The "send-pr" system > > > doesn't cut it, and most people are unaware of how to file a > > > decent bug report. It doesn't help when the process involves > > > another computer, a serial cable, recompiling a kernel to use > > > a serial console and turn DDB support on, special configuration > > > for system dump images, and changing the size of your swap > > > partition to support the amount of RAM you have put into the > > > machine. > > > > Speaking as someone who is about to step off the deep end and > > start trying to actually run and test -CURRENT on my system here at > > home, I believe that this kind of resource would be vitally important. > > > > In contrast, I've had a few crashes this past week from other > > programs here on my PowerBook G4 running MacOS X (primarily Chimera, > > based on the Mozilla Gecko engine with native Aqua interface), and > > they have made it very easy for me to report crashes. They have > > integrated tools to extract the maximum amount of information from > > the system as to exactly what other programs were running, what the > > program stack was, and a whole host of other things. All I have to > > do is type in my e-mail address, optionally describe what I was > > trying to do at the time, and have a functioning Internet connection > > so that they can upload the reports. I'd share some examples with > > you, but they are *huge*. > > For a while, there was a discussion about starting this capability with > panic() reporting a stack trace. I believe someone even did some > implementation work. Any ideas where this stands? John Baldwin implemented something like this, but you need DDB compiled in for it to work. And if you have DDB compiled in, how hard is it to type `trace'? Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message