From owner-freebsd-questions@freebsd.org Wed Dec 7 01:27:10 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F16CC6A026 for ; Wed, 7 Dec 2016 01:27:10 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 53E5CA18; Wed, 7 Dec 2016 01:27:10 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id A652B654A; Wed, 7 Dec 2016 01:27:09 +0000 (UTC) To: freebsd-questions@freebsd.org, shrikanthbaikunje@gmail.com Subject: Re: (malloc) Unsupported character in malloc options: 'o' In-Reply-To: Message-Id: <20161207012709.A652B654A@freefall.freebsd.org> Date: Wed, 7 Dec 2016 01:27:09 +0000 (UTC) From: jbeich@freebsd.org (Jan Beich) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2016 01:27:10 -0000 Shrikanth B writes: > I am on FreeBSD 10.1. > When i run "ln -s 'abort:true' /etc/malloc.conf" as mentioned in > JEMALLOC(3) man page, i get flooded with following errors: > > (malloc) Unsupported character in malloc options: 'o' > > (malloc) Unsupported character in malloc options: 't' > > (malloc) Unsupported character in malloc options: ':' > > (malloc) Unsupported character in malloc options: 't' > > (malloc) Unsupported character in malloc options: 'e' > > Any solution for this? jemalloc 3.0 or later as part of libc in FreeBSD 10.0 or later is no longer compatible with phkmalloc syntax: MALLOC_OPTIONS vs. MALLOC_CONF. "(malloc)" prefix above indicates jemalloc, not phkmalloc. So, the error comes from linking against old libc e.g., from FreeBSD 9.3. If you can't rebuild the affected component against new libc try setting both environment variables instead of using /etc/malloc.conf. $ export MALLOC_OPTIONS=A MALLOC_CONF=abort:true $ /path/to/app