This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nss/22184] Memory leak(s) in getaddrinfo_a
- From: "tim.ruehsen at gmx dot de" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 25 Sep 2017 10:24:44 +0000
- Subject: [Bug nss/22184] Memory leak(s) in getaddrinfo_a
- Auto-submitted: auto-generated
- References: <bug-22184-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22184
--- Comment #6 from Tim Rühsen <tim.ruehsen at gmx dot de> ---
(In reply to Carlos O'Donell from comment #4)
> You must use -rpath to build a binary that uses the new libraries, otherwise
> this uses your system libraries.
>
> Please see this document for steps on how to do that:
> https://sourceware.org/glibc/wiki/Testing/Builds
Ok, looks now like
$ ldd gai_leak
linux-vdso.so.1 (0x00007ffd743a2000)
libanl.so.1 => /usr/tim/src/glibc/mybuild//resolv/libanl.so.1
(0x00007f93fddd3000)
libpthread.so.0 => /usr/tim/src/glibc/mybuild//nptl/libpthread.so.0
(0x00007f93fdbb5000)
libc.so.6 => /usr/tim/src/glibc/mybuild/libc.so.6 (0x00007f93fd812000)
/usr/tim/src/glibc/mybuild//elf/ld.so => /lib64/ld-linux-x86-64.so.2
(0x00007f93fe1da000)
but can't get valgrind working (what tool do you use ?).
$ gcc -g
-Wl,-rpath=${GLIBC}:${GLIBC}/math:${GLIBC}/elf:${GLIBC}/dlfcn:${GLIBC}/nss:${GLIBC}/nis:${GLIBC}/rt:${GLIBC}/resolv:${GLIBC}/crypt:${GLIBC}/nptl:${GLIBC}/dfp
-Wl,--dynamic-linker=${GLIBC}/elf/ld.so gai_leak.c -o gai_leak -lanl
-lpthread
$ valgrind ./gai_leak
...
valgrind: Fatal error at startup: a function redirection
valgrind: which is mandatory for this platform-tool combination
valgrind: cannot be set up. Details of the redirection are:
valgrind:
valgrind: A must-be-redirected function
valgrind: whose name matches the pattern: strlen
valgrind: in an object with soname matching: ld-linux-x86-64.so.2
valgrind: was not found whilst processing
valgrind: symbols from the object with soname: ld-linux-x86-64.so.2
valgrind:
valgrind: Possible fixes: (1, short term): install glibc's debuginfo
valgrind: package on this machine. (2, longer term): ask the packagers
valgrind: for your Linux distribution to please in future ship a non-
valgrind: stripped ld.so (or whatever the dynamic linker .so is called)
valgrind: that exports the above-named function using the standard
valgrind: calling conventions for this platform. The package you need
valgrind: to install for fix (1) is called
valgrind:
valgrind: On Debian, Ubuntu: libc6-dbg
valgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo
valgrind:
valgrind: Note that if you are debugging a 32 bit process on a
valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo
valgrind: package (e.g. libc6-dbg:i386).
valgrind:
valgrind: Cannot continue -- exiting now. Sorry.
--
You are receiving this mail because:
You are on the CC list for the bug.