|
From: Gao, J. <JG...@se...> - 2003-09-24 15:49:52
|
> my_program must rely on at least one shared object.
I want to ask the reverse question: if my_program relies on one
shared object, will valgrind always work with my_program?
The reason for my question is: if the answer is yes, then we can
come up a way to "remove" (at least in practical sense) this
requirement. For example:
Ship a dummy shared object, see, vgdummy.so, with valgrind. It
has one function, see, VG_dummy() which basically does nothing. The
user program can call VG_dummy() and linked with vgdummy.so, then the
valgrind will work with the user program. We can make the VG_dummy() as
a Valgrind MACRO if desired.
Just a quick thought. Correct me if I am smoking cracks:-)
Jiafu
-----Original Message-----
From: Nicholas Nethercote [mailto:nj...@ca...]
Sent: Wednesday, September 24, 2003 11:29 AM
To: Todd Berendes
Cc: val...@li...
Subject: Re: [Valgrind-users] Valgrind ignores program if linked with
-static flag
On Wed, 24 Sep 2003, Todd Berendes wrote:
> Valgrind does not work if -static is specified on the link line.
From the FAQ:
Q5. I try running "valgrind my_program", but my_program runs normally,
and Valgrind doesn't emit any output at all.
A5. Is my_program statically linked? Valgrind doesn't work with
statically linked binaries. my_program must rely on at least one
shared object. To determine if a my_program is statically linked,
run:
ldd my_program
It will show what shared objects my_program relies on, or say:
not a dynamic executable
if my_program is statically linked.
N
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
Valgrind-users mailing list Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-users
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. If
you are not the intended recipient, you should delete this message. Any
disclosure, copying, or distribution of this message, or the taking of any
action based on it, is strictly prohibited.
|