From owner-freebsd-current Thu Jan 16 14:46:17 2003 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 666D337B401 for ; Thu, 16 Jan 2003 14:46:15 -0800 (PST) Received: from storming.org (MG034063.user.veloxzone.com.br [200.165.34.63]) by mx1.FreeBSD.org (Postfix) with SMTP id D3D4843F3F for ; Thu, 16 Jan 2003 14:46:13 -0800 (PST) (envelope-from fred@storming.org) Received: (qmail 94445 invoked by uid 1000); 16 Jan 2003 20:46:01 -0200 Date: Thu, 16 Jan 2003 20:46:01 -0200 From: Fred Souza To: current@freebsd.org Subject: mpg123 dumping core Message-ID: <20030116224601.GA93341@torment.storming.org> Reply-To: fred@storming.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline X-Sender: fred@storming.org 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 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, Has anyone besides me experienced mpg123 dumping core on recent (from 10/01/03 builds and on) -CURRENT builds? I was using it perfectly, then I reinstalled the port to include a couple of cosmetic patches of mine (they don't do ANYTHING that could cause this - it's only to change the case of a few messages mpg123 displays), and after that from time to time mpg123 dumps core after a signal 11. The version is 0.59r, and before that I had been using it for a long time without this problem. A quick look at the core file tells that the function sigprocmask() was the last thing executed before the fault. I then remembered seeing on LICQ's documentation that it wouldn't run if it had been compiled with a gcc of version different from which QT was, and I thought something similar could be happening with mpg123. I then cvsup'd, recompiled the kernel and world, then reinstalled all ports related to mpg123. It now segfaults with longer periods of time, but still does. Any pointers? Thank you all, Fred --=20 "If things were left to chance, they'd be better." --zhXaljGHf11kAtnf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+JzYpKbRS1GgW4fYRAprBAJ9os5rUlxblNcXXK1JKquHAVvaD8gCfWYxT /xbokcbn+QhKPaVFqUuS7ts= =Rhqf -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message