Date: Tue, 17 Jan 2006 17:26:23 -0700 (MST) From: Mike Brown <mike@skew.org> To: freebsd-ports@freebsd.org Subject: Re: f2c problems with the new malloc (Fwd: [ports-amd64@pointyhat.freebsd.org: arpack-96 failed on amd64 7]) Message-ID: <200601180026.k0I0QNIk000992@chilled.skew.org> In-Reply-To: <20060117171416.16894.qmail@web32912.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601180026.k0I0QNIk000992>