This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc 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] |
On 23 Jun 2016 19:25, Florian Weimer wrote: > On 06/23/2016 07:16 PM, Siddhesh Poyarekar wrote: > > On Thu, Jun 23, 2016 at 12:57:17PM -0400, Zack Weinberg wrote: > >> Is there a well-documented way to run the tests under valgrind? > > > > I don't think so, but it ought to be sufficient to run valgrind > > --trace-children=yes for all of make check. Dead slow, but I don't > > see why it shouldn't work. > > > > Maybe this is a good candidate for enhancement in glibc to allow > > running individual tests under valgrind, something like > > 'make valgrind-check'. > > Running tests under valgrind is one thing. Interpreting the errors is > another. > > On some architectures, running valgrind on a non-installed libc gives > rather poor results. Some versions do not recognize malloc as such, and > on some architectures, the suppression files are inactive because the > libc paths do not match the hard-coded expectations of valgrind. not only that, but valgrind frequently needs to be updated whenever a new glibc release is made (to tweak internal false positives). if we tried to use that against git master, i'm afraid it'd always be broken. -mike
Attachment:
signature.asc
Description: Digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |