From owner-freebsd-ports@FreeBSD.ORG Tue Jan 31 20:08:57 2006 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9560916A422; Tue, 31 Jan 2006 20:08:57 +0000 (GMT) (envelope-from novel@smtp.hispeed.ch) Received: from smtp.hispeed.ch (mxout.hispeed.ch [62.2.95.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id E94CF43D46; Tue, 31 Jan 2006 20:08:56 +0000 (GMT) (envelope-from novel@smtp.hispeed.ch) Received: from underworld.novel.ru (ts1-a23.Saratov.dial.rol.ru [194.186.150.23]) (authenticated bits=0) by smtp.hispeed.ch (8.12.6/8.12.6/taifun-1.0) with ESMTP id k0VK8nTD015870; Tue, 31 Jan 2006 21:08:52 +0100 Date: Tue, 31 Jan 2006 23:09:46 +0000 From: Roman Bogorodskiy To: clsung@FreeBSD.org Message-ID: <20060131230946.GA30825@underworld.novel.ru> Mail-Followup-To: clsung@FreeBSD.org, ports@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline X-PGP: http://people.freebsd.org/~novel/novel.key.asc User-Agent: Mutt/1.5.11 X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on smtp-04.tornado.cablecom.ch X-Virus-Status: Clean X-DCC-spamcheck-02.tornado.cablecom.ch-Metrics: smtp-04.tornado.cablecom.ch 32701; Body=2 Fuz1=2 Fuz2=2 Cc: ports@FreeBSD.org Subject: FreeBSD Port: net-im/centericq: doesn't work on -CURRENT X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2006 20:08:57 -0000 --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, More than year ago I had problems with centericq[1] coredumping after connecting to the icq server. Now I have exatly the same problem, but malloc.conf tricks doesn't help this time. I'm using centericq 4.21.0 on -CURRENT/amd64. Any ideas how to fix that? 1: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=687769+0+archive/2004/freebsd-ports/20040829.freebsd-ports Roman Bogorodskiy --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iQCVAwUBQ9/uOoB0WzgdqspGAQIjMwQAo6CbHzxiRl1mFkpu1HJj9ntIiXH3M83t u5CsjxVvuvekJMj/DI/ciysfkjU4vMbrJGbZrh7f5b1qPKXx9UQh9z2uoKiLl+7T AuJVaiXrRaNGmNG4M5q7mWNJIrjE8vHqjIonDyAytYSIn4dp4IYyXUDng4m1sr2u I4a1u1FBWhE= =sMst -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q--