From owner-freebsd-current Mon Oct 4 23:34:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 0122B153D4 for ; Mon, 4 Oct 1999 23:34:20 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA33418; Tue, 5 Oct 1999 08:33:55 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199910050633.IAA33418@gratis.grondar.za> To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: CVSup core dumps Date: Tue, 05 Oct 1999 08:33:54 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've seen a few reports that CVSup has suddenly started dumping > core on a segmentation violation under -current, but I need more > information. For starters, I would like to know whether the static > binary (ports/net/cvsup-bin) works or not under the very latest > -current on the i386. Could somebody please check that and report > back to the list? I can't sacrifice my i386 -current machine to the > cause right now. The static binary seems to be OK an a 3-day-old CURRENT. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message