Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [FYI] jemalloc and valgrind
Date: Thu, 8 Sep 2016 23:12:50 +0200	[thread overview]
Message-ID: <20160908231250.6aceffd2@free-electrons.com> (raw)
In-Reply-To: <D7C5A212-77BA-44BA-9FDE-35F0CA5FAA86@exablox.com>

Hello,

On Thu, 8 Sep 2016 13:54:00 -0700, Charles Hardin wrote:
> So, we hit an oddity on a ?debug? build which turned out to be that if we have
> valgrind installed - jemalloc would race

What do you mean by "would race" ?

> and if it got build before valgrind then
> it would not detect it.
> 
> I?ll try to make this a format patch later - but this is off another tree and so simple
> that if someone wants to add it - I would suggest you do.

It would be better if you could make an official patch, since your
patch below looks almost good, it only needs a proper commit log +
correct submission.

> 
> diff --git a/package/jemalloc/jemalloc.mk b/package/jemalloc/jemalloc.mk
> index 7086dfa..71d6200 100644
> --- a/package/jemalloc/jemalloc.mk
> +++ b/package/jemalloc/jemalloc.mk
> @@ -11,5 +11,10 @@ JEMALLOC_LICENSE = BSD-2c
>  JEMALLOC_LICENSE_FILES = COPYING
>  JEMALLOC_INSTALL_STAGING = YES
>  
> +ifeq ($(BR2_PACKAGE_VALGRIND),y)
> +JEMALLOC_DEPENDENCIES += valgrind
> +JEMALLOC_CONF_OPTS += --enable-valgrind

Please add:

else
JEMALLOC_CONF_OPTS += --disable-valgrind

> +endif

Also, for good measure:

HOST_JEMALLOC_CONF_OPTS += --disable-valgrind

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2016-09-08 21:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 20:54 [Buildroot] [FYI] jemalloc and valgrind Charles Hardin
2016-09-08 21:12 ` Thomas Petazzoni [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160908231250.6aceffd2@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox