qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] tests: set MALLOC_PERTURB_ to expose memory bugs
Date: Fri, 17 May 2013 13:16:35 +0200	[thread overview]
Message-ID: <CAJSP0QUMcvKJ-FM-3tH_WrPMKQCMQhWHFtCGRE+UN1FacmgmTQ@mail.gmail.com> (raw)
In-Reply-To: <20130517100738.GF2342@redhat.com>

On Fri, May 17, 2013 at 12:07 PM, Daniel P. Berrange
<berrange@redhat.com> wrote:
> Rather than setting MALLOC_PERTURB_=1 unconditionally in the Makefile
> though, it ought to honour any existing MALLOC_PERTURB_ env variable
> the user has set. That could let automated test harness run repeatedly
> with random MALLOC_PERTURB_, while still giving a deterministic value
> for developers by default.

Good point.  Will fix in v2.

Stefan

  parent reply	other threads:[~2013-05-17 11:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17  8:52 [Qemu-devel] [PATCH] tests: set MALLOC_PERTURB_ to expose memory bugs Stefan Hajnoczi
2013-05-17  9:54 ` Markus Armbruster
2013-05-17 10:07   ` Daniel P. Berrange
2013-05-17 10:58     ` Markus Armbruster
2013-05-17 12:52       ` Lucas Meneghel Rodrigues
2013-05-17 11:16     ` Stefan Hajnoczi [this message]
2013-05-17 12:49     ` Lucas Meneghel Rodrigues
2013-05-19 16:51     ` Richard W.M. Jones
2013-05-17 11:15   ` Stefan Hajnoczi
2013-05-17 12:50     ` Lucas Meneghel Rodrigues

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=CAJSP0QUMcvKJ-FM-3tH_WrPMKQCMQhWHFtCGRE+UN1FacmgmTQ@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=lmr@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).