|
From: Nicholas N. <nj...@ca...> - 2004-08-20 08:04:15
|
On Thu, 19 Aug 2004, Robert Walsh wrote: > One way of doing this is to have Valgrind open a socket and check it for > requests generated by a companion client program every so often. Sounds > like it might slow things down, though. Should be simple to code up and > measure, though. Another recent discussion was based around using signals, but letting the user specify which signal on the command line. So you could, for example, using SIGINT for leak checking on Ctrl-C in interactive programs (maybe using a prompt which asks, when you get a SIGINT, whether to do a leak-check or just treat the signal normally). N |