On Sat, 22 Apr 2000, Jamie Lokier wrote:
> I'd really like a tool that can check for missing locks, redundant
> locks, operations that should be atomic, missing memory barriers, that
> sort of thing. It's not easy is it? :-)
It's provably equivalent to the halting problem, assuming you even have
enough info in the source to automatically identify things that need
atomicity. Anything with recursion or coroutines is liable to make it very
unhappy.
That said, quite a bit can be done with runtime checks ala the spinlock
debugging code that can't be done by static analysis.
-- "Love the dolphins," she advised him. "Write by W.A.S.T.E.."- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:21 EST