This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Use of mcheck during GDB development

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.
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]