From owner-freebsd-questions Wed May 3 13: 3:59 2000 Delivered-To: freebsd-questions@freebsd.org Received: from infowest.com (ns1.infowest.com [204.17.177.10]) by hub.freebsd.org (Postfix) with ESMTP id B90DD37B533 for ; Wed, 3 May 2000 13:03:56 -0700 (PDT) (envelope-from root@infowest.com) Received: by infowest.com (Postfix, from userid 0) id 73FBE20FBE; Wed, 3 May 2000 14:02:43 -0600 (MDT) To: questions@freebsd.org Subject: licq dumps core - Licq Segmentation Violation Detected [Manager Thread]. Reply-To: From: "Aaron D. Gifford" Message-Id: <20000503200243.73FBE20FBE@infowest.com> Date: Wed, 3 May 2000 14:02:43 -0600 (MDT) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The licq port was working fine for me before I did a recent make world to upgrade from 4.0-STABLE of sometime in early March 2000 to 4.0-STABLE of May 2, 2000. At first, I had tried to use the same licq binary I built in March, but it would dump core with the error: $ licq Licq Segmentation Violation Detected [Manager Thread]. Abort trap (core dumped) So, I deinstalled the port and rebuilt it. I admittedly have NOT yet tried rebuilding all the other ports it depends on since that's a rather large number and I'd like to find another solution if possible. Any ideas about why it was working before but is now freaking out? Aaron out. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message