Warp wrote:
> Darren New <dne### [at] sanrrcom> wrote:
>> When 
>> your job is interfacing half a dozen different things together, you 
>> can't really trust that there's no buffer overruns and so on.
> 
>   Even though C and C++ are very unsafe languages in that regard, some
> tools exist which can catch most of these problems, such as valgrind.

Except it's not my code, so I couldn't fix it if I wanted to. :-) And 
valgrind on real-time hardware I/O isn't going to help a whole lot. :-)

But yah, I've used valgrind and one other popular one whose name I don't 
remember? Pforce?

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?

Post a reply to this message