Date: Sun, 19 Feb 2006 03:07:37 GMT From: SANETO Takanori <sanewo@ba2.so-net.ne.jp> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/93548: lang/ezm3 uses old malloc which may complain about unknown char in MALLOC_OPTIONS Message-ID: <200602190307.k1J37bDB000307@www.freebsd.org> Resent-Message-ID: <200602190310.k1J3A9DV061025@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 93548 >Category: ports >Synopsis: lang/ezm3 uses old malloc which may complain about unknown char in MALLOC_OPTIONS >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Feb 19 03:10:08 GMT 2006 >Closed-Date: >Last-Modified: >Originator: SANETO Takanori >Release: 7.0-CURRENT >Organization: an individual >Environment: FreeBSD muse.sanewo.ddo.jp 7.0-CURRENT FreeBSD 7.0-CURRENT #822: Sun Jan 15 06:08:54 JST 2006 root@muse.sanewo.ddo.jp:/export/usr/obj/usr/src/sys/MUSE i386 >Description: ezm3 contains modified version of old (phk) malloc implementaion in m3core.a. This cause incompatibility in interpretation of MALLOC_OPTIONS environment variable and /etc/malloc.conf setting. When, for example, 'k' is in these settings, application built with m3 (e.g. cvsup) will submit warning "unknown char in MALLOC_OPTIONS". >How-To-Repeat: rebuild ezm3 and cvsup under current. run cvsup with MALLOC_OPTIONS=k. >Fix: replace malloc in ezm3 under CURRENT, or at least, refer different env/file for malloc setting for ezm3 (e.g., M3_MALLOC_OPTIONS and /etc/m3_malloc.conf). >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602190307.k1J37bDB000307>