This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug libc/804] malloc/tst-mtrace minor problem
- From: "gschafer at zip dot com dot au" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 12 May 2005 00:24:04 -0000
- Subject: [Bug libc/804] malloc/tst-mtrace minor problem
- References: <20050325124117.804.balducci@units.it>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- Additional Comments From gschafer at zip dot com dot au 2005-05-12 00:24 -------
Yes, confirmed. This is a real bug, albeit a very minor one. But the suggested
fix is not the correct one.
The Glibc testsuite normally runs binaries using:
elf/ld-linux.so.2 --library-path blah:blah:blah
to overcome the problem of having the dynamic linker hardwired to a name which
may not exist yet. This also explains why most folks won't see the problem
(those specifying a prefix where a dynamic linker already exists).
In this instance, the existing technique won't work because the invocation of
the mtrace perl script (from inside tst-mtrace.sh) runs the `tst-mtrace' binary
directly.
A possible fix is to run the mtrace perl script without using the binary ie:
just use the data file alone. This makes it work for me. But I'm unsure whether
running the (optional) binary will make a difference for what is being tested here.
Anyway, patch to follow.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |gschafer at zip dot com dot
| |au
Summary|malloc/tst-mtrace linked w/ |malloc/tst-mtrace minor
|wrong dynamic-linker |problem
|directive |
http://sources.redhat.com/bugzilla/show_bug.cgi?id=804
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.