guy keren wrote:
when you can use valgrind - most other things are pretty useless.
did you encounter a memory-handling bug that valgrind failed to catch,
while another tool (such as libsafe) did catch?
note: i never used libsafe, so i might be missing something - i simply
compared valgrind to many other available tools in the past, and
nothing (except for commercial software such as purify) came close.
AFAIK Valgrind does not detect neither stack nor static buffer overflows
at all.
Gilad
--
Gilad Ben-Yossef
Chief Coffee Drinker
Codefidence Ltd.
The code is free, your time isn't.(TM)
Web: http://codefidence.com
Email: [EMAIL PROTECTED]
Office: +972-8-9316883 ext. 201
Fax: +972-8-9316885
Mobile: +972-52-8260388
