|
From: tony c. <ant...@ya...> - 2007-01-23 15:23:06
|
Hi=0A=0AI am using Valgrind 3.0.1 (Red Hat 9.0).=0A=0AAnyway, I am doing a = --leak-check=3Dfull on my valgrind command which,=0Awhen the process exits,= does a leak check. Problem is, the process I am =0Arunning valgrind on is= like a system process that pretty much is in an endless=0Aloop, waiting fo= r messages and processing them. It never terminates.=0A=0AI know in purify= if you killed the process with a certain signal (like -15 but not -9)=0Apu= rify would terminate the process and do all the leak checking. However, th= is=0Adoes not seem to work with valgrind.=0A=0ADoes anyone know how I can t= erminate the process and get valgring to check for=0Aleaks?=0A=0A=0AThanks= =0ATony=0A=0Ap.s., I could not find anything in the FAQ =0A=0A=0A=0A=0A=0A= =0A =0A____________________________________________________________________= ________________=0AHave a burning question? =0AGo to www.Answers.yahoo.com= and get answers from real people who know. |
|
From: Tom H. <to...@co...> - 2007-01-23 15:26:48
|
In message <543...@we...>
tony chamberlain <ant...@ya...> wrote:
> I am using Valgrind 3.0.1 (Red Hat 9.0).
>
> Anyway, I am doing a --leak-check=full on my valgrind command which,
> when the process exits, does a leak check. Problem is, the process I am
> running valgrind on is like a system process that pretty much is in an endless
> loop, waiting for messages and processing them. It never terminates.
>
> I know in purify if you killed the process with a certain signal
> (like -15 but not -9) purify would terminate the process and do all
> the leak checking. However, this does not seem to work with
> valgrind.
I think you will find that if you use a less prehistoric version
of valgrind then it will do a leak check when you kill it.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Nicholas N. <nj...@cs...> - 2007-01-23 22:48:58
|
On Tue, 23 Jan 2007, Tom Hughes wrote: >> I am using Valgrind 3.0.1 (Red Hat 9.0). >> >> Anyway, I am doing a --leak-check=full on my valgrind command which, >> when the process exits, does a leak check. Problem is, the process I am >> running valgrind on is like a system process that pretty much is in an endless >> loop, waiting for messages and processing them. It never terminates. >> >> I know in purify if you killed the process with a certain signal >> (like -15 but not -9) purify would terminate the process and do all >> the leak checking. However, this does not seem to work with >> valgrind. > > I think you will find that if you use a less prehistoric version > of valgrind then it will do a leak check when you kill it. 3.2.2 was released yesterday, you might like to try that. Also, you can embed client requests in your code to do leak checking at certain points without terminating the program. I think the relevant request is called VALGRIND_DO_LEAK_CHECK -- see the Memcheck section of the manual. Nick |