|
From: Gao, J. <JG...@se...> - 2003-09-24 16:18:41
|
> Doesn't seem like much of an improvement to me... the user still has to know about > static linking causing problems. Once they know that, it's > rarely(?) a problem to fix it. How about if the user program just have static libraries? It would be inconvinent to change the obtain a .so library (if he can) and make file just to use valgrind. The user also has to change the make back if he want to keep the program works as before. It is true the user has to change the makefile to use the dummy .so, but it is only one time change. > I think a better alternative is to use a patch Olly Betts submitted a while back: it makes Valgrind's startup script check with 'ldd' whether the program is statically linked, and aborts with a helpful explanatory message if so. Can anyone see any problems with this? If not, I'll consider committing it. I like this. How about we do both? :-) N 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. |