search for: sewardj

http://developer.kde.org/~sewardj/ Valgrind is a GPL'd tool to help you find memory-management problems in your programs. When a program is run under Valgrind's supervision, all reads and writes of memory are checked, and calls to malloc/new/free/delete are intercepted. As a result, Valgrind can detect problems such as:...

This email isn't really LLVM specific, but is definately useful for LLVM people so.... I've downloaded and installed "valgrind" (http://developer.kde.org/~sewardj/), an open source "purify" replacement. It is actually quite a bit nicer than purify is, as it doesn't require you to recompile or modify your executables _at all_ to run them (it also seems quite fast). Anyway, if you suspect you have memory error issues, I'd recommend trying i...

Is it already known that R does not free the memory that it allocates during start-up (~10MB) when it exits? If so, are there currently any plans to address this problem? I noticed that the 1.6.0 beta leaks slightly more memory (~300k) than the 1.5.1 stable version. I am working on a project that links with the R library, and there is a question about unloading and later re-loading the

En r?ponse ? Matt Zimmerman <mdz@debian.org>: > > In the case of hardware support, the benefits are still not there. > > Are you suggesting that BSD licensing is problematic for hardware > vendors, > or problematic for other users of the software in the context of > hardware support? Not at all. But what I said is that there is no proof that hardware vendors only want