From owner-freebsd-current  Fri Sep 12 13:31:40 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id NAA06313
          for current-outgoing; Fri, 12 Sep 1997 13:31:40 -0700 (PDT)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA06308
          for <current@freebsd.org>; Fri, 12 Sep 1997 13:31:37 -0700 (PDT)
Received: from austin.polstra.com (jdp@localhost)
	by austin.polstra.com (8.8.7/8.8.5) with ESMTP id NAA02172;
	Fri, 12 Sep 1997 13:29:57 -0700 (PDT)
Message-Id: <199709122029.NAA02172@austin.polstra.com>
To: mika ruohotie <bsdcur@shadows.aeon.net>
cc: current@freebsd.org
Subject: Re: cvsup 
In-reply-to: Your message of "Fri, 12 Sep 1997 22:35:02 +0300."
    <199709121935.WAA26029@shadows.aeon.net> 
Date: Fri, 12 Sep 1997 13:29:57 -0700
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Thanks for the info about the CVSup crashes you've been having.

> > binary, installed the package, built the port.)  Also, please send me
> 
> built, few times, i never use packages. =)

Would you be willing to take a static binary that I've compiled with
debugging symbols, run it under gdb, and (if it crashes) send me the
stack backtrace (output of gdb's "where" command)?  I haven't had
good luck with M3 core dumps when shared libraries are involved.
Also, unless our systems are fairly close in sync, there's a good
chance that the gdb here won't be able to read a core file generated
on your machine.

It will also be interesting to see whether the static binary even
fails at all.  If it doesn't, I'll have something new for you to
try.

John