From owner-freebsd-ports@FreeBSD.ORG Wed Jan 18 00:26:31 2006 Return-Path: X-Original-To: freebsd-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 B4E7116A420 for ; Wed, 18 Jan 2006 00:26:31 +0000 (GMT) (envelope-from mike@skew.org) Received: from chilled.skew.org (skew.org [65.101.207.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8922043D79 for ; Wed, 18 Jan 2006 00:26:24 +0000 (GMT) (envelope-from mike@skew.org) Received: from chilled.skew.org (localhost.skew.org [127.0.0.1]) by chilled.skew.org (8.13.1/8.13.1) with ESMTP id k0I0QNST000993 for ; Tue, 17 Jan 2006 17:26:23 -0700 (MST) (envelope-from mike@chilled.skew.org) Received: (from mike@localhost) by chilled.skew.org (8.13.1/8.13.1/Submit) id k0I0QNIk000992 for freebsd-ports@freebsd.org; Tue, 17 Jan 2006 17:26:23 -0700 (MST) (envelope-from mike) From: Mike Brown Message-Id: <200601180026.k0I0QNIk000992@chilled.skew.org> In-Reply-To: <20060117171416.16894.qmail@web32912.mail.mud.yahoo.com> To: freebsd-ports@freebsd.org Date: Tue, 17 Jan 2006 17:26:23 -0700 (MST) X-Whoa: whoa. X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=UTF-8 Subject: Re: f2c problems with the new malloc (Fwd: [ports-amd64@pointyhat.freebsd.org: arpack-96 failed on amd64 7]) 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: Wed, 18 Jan 2006 00:26:31 -0000 pfgshield-freebsd@yahoo.com wrote: > Hi; > > f2c, which arpack uses to generate headers, is having problems with the new > malloc on amd64 (messages follow). If the problem is difficult to find perhaps > we should stop generating those headers: I think no port uses them. I maintain a port that uses Python C extensions (it builds the extensions, then makes use of them later in the build), and it is having similar "(malloc) Corrupted redzone" problems on fbsd 7/amd64 according to the latest unbuildable-ports reports. Specifically, it's python: (malloc) Corrupted redzone 1 byte after 0x8062d9340 (size 68) (0x0) python: (malloc) Corrupted redzone 2 bytes after 0x8062d9340 (size 68) (0x0) python: (malloc) Corrupted redzone 3 bytes after 0x8062d9340 (size 68) (0x0) python: (malloc) Corrupted redzone 4 bytes after 0x8062d9340 (size 68) (0x0) I've never seen this error before and have no way of debugging it. I'm hesitant to mark the port as broken if this is a temporary problem with just this one unstable platform. Any info/guidance appreciated... Thanks Mike