This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/21336] __libc_res_nsearch() leak?
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 04 Apr 2017 19:27:59 +0000
- Subject: [Bug libc/21336] __libc_res_nsearch() leak?
- Auto-submitted: auto-generated
- References: <bug-21336-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21336
--- Comment #18 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Rob Krakora from comment #17)
> Yes, I would LOVE to use Valgrind. However, we are on a ARM v5 and Valgrind
> ARM support starts at v7.
I assume you could perform memory leak testing on a different architecture than
your production architecture. The important bit is to increase test coverage.
Architecture-specific memory leaks happen, but are not the norm.
--
You are receiving this mail because:
You are on the CC list for the bug.