From: Bernhard Voelker <mail@bernhard-voelker.de>
To: kerolasa@gmail.com, Karel Zak <kzak@redhat.com>
Cc: Boris Egorov <egorov@linux.com>, util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 0/6] pull: almost working AddressSanitizer support
Date: Wed, 12 Nov 2014 22:08:40 +0100 [thread overview]
Message-ID: <5463CC58.9070609@bernhard-voelker.de> (raw)
In-Reply-To: <CAG27Bk2-c4_AsqCsBd+uBkkcvX0CSJPW+Q2+JndyGts=ZE1rmw@mail.gmail.com>
On 11/12/2014 04:02 PM, Sami Kerola wrote:
> On 12 November 2014 14:25, Karel Zak <kzak@redhat.com> wrote:
>> On Tue, Nov 11, 2014 at 10:49:02PM +0000, Sami Kerola wrote:
>>> printf(_("Setting up swapspace version %d, size = %s (%ju bytes)\n"),
>>> version, strsz, sz);
>>> + free(strsz);
>>
>> free-before-exit, you know what I think about it, right? :)
>
> Normally I would agree, but this case is bizarre. The mkswap will
> return 1 when compiled with clang -fsanitize=address without any
> message what is wrong. That's probably clang bug, which is a different
> topic all together. Adding the free() calls seems to make the
> immediate tests failure issue to go away, that is needed to automate
> sanitize. In case travis && address sanitation is not needed at all
> then these changes does not make sense.
In coreutils, we're using a macro IF_LINT as condition for such
free() calls, and for tools like Coverity, we're turning it on.
Have a nice day,
Berny
next prev parent reply other threads:[~2014-11-12 21:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 21:49 [PATCH 0/6] pull: almost working AddressSanitizer support Sami Kerola
2014-11-10 21:49 ` [PATCH 1/6] build-sys: make scanf_cv_alloc_modifier to work [AddressSanitizer] Sami Kerola
2014-11-11 2:10 ` Mike Frysinger
2014-11-11 22:51 ` Sami Kerola
2014-11-10 21:49 ` [PATCH 2/6] tests: fix memory leak [AddressSanitizer] Sami Kerola
2014-11-10 21:49 ` [PATCH 3/6] tests: add mkswap size printout to expected output Sami Kerola
2014-11-10 21:49 ` [PATCH 4/6] libmount: fix memory overflow [AddressSanitizer] Sami Kerola
2014-11-18 12:06 ` Karel Zak
2014-11-10 21:49 ` [PATCH 5/6] tests: skip kill -SEGV test when running AddressSanitizer Sami Kerola
2014-11-10 21:49 ` [PATCH 6/6] tests: mark python libmount tests known to fail with AddressSanitizer Sami Kerola
2014-11-11 2:12 ` Mike Frysinger
2014-11-11 21:16 ` Sami Kerola
2014-11-11 7:17 ` [PATCH 0/6] pull: almost working AddressSanitizer support Boris Egorov
2014-11-11 22:08 ` Sami Kerola
2014-11-11 22:49 ` Sami Kerola
2014-11-12 14:25 ` Karel Zak
2014-11-12 15:02 ` Sami Kerola
2014-11-12 19:51 ` Mike Frysinger
2014-11-12 20:50 ` Sami Kerola
2014-11-13 14:48 ` Karel Zak
2014-11-12 21:08 ` Bernhard Voelker [this message]
2014-11-18 12:01 ` Karel Zak
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=5463CC58.9070609@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=egorov@linux.com \
--cc=kerolasa@gmail.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.