From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: Florian Weimer <fweimer@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Use of mcheck during GDB development
Date: Tue, 15 Nov 2016 22:11:00 -0000 [thread overview]
Message-ID: <fe71b281fe78c7d22c18e66909a90c1c@polymtl.ca> (raw)
In-Reply-To: <fae8c1e0-7a35-b3d1-d2a5-3e852697a38d@redhat.com>
On 2016-11-15 17:07, Pedro Alves wrote:
> On 11/15/2016 09:58 PM, Simon Marchi wrote:
>> On 2016-11-15 15:50, Pedro Alves wrote:
>>> Yeah, or address sanitizer, which would be closer to being
>>> something you could always have on. Valgrind is too heavyweight
>>> for everyday use. I believe we're not asan clean yet, unfortunately,
>>> but we're slowly getting there.
>>
>> I occasionally build GDB with ASAN when chasing specific bugs, and
>> it's
>> been clean for my practical purposes. Except for many warnings in
>> libpython at startup, I don't know whether they're real or false
>> positives.
>
> I meant when running the GDB testsuite against it. Do you know whether
> asan
> vs non-asan is regression free for you? I haven't tried in a while.
Ah no I've never tested that. But if we have enough resources for the
buildbot, we should run an x86 job with it enabled.
next prev parent reply other threads:[~2016-11-15 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 16:00 Florian Weimer
2016-11-15 20:03 ` Pedro Alves
2016-11-15 20:22 ` Florian Weimer
2016-11-15 20:46 ` Mike Frysinger
2016-11-15 20:50 ` Pedro Alves
2016-11-15 21:58 ` Simon Marchi
2016-11-15 22:07 ` Pedro Alves
2016-11-15 22:11 ` Simon Marchi [this message]
2016-11-15 21:28 ` Yao Qi
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=fe71b281fe78c7d22c18e66909a90c1c@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=fweimer@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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