[taneq]

> This exploit seems to lie at the intersection of several things that I guess might indicate a higher-than-average risk of exploitability: shared memory, special provisions for debugging access to running processes, complicated and unintuitive (if not broken) semantics, and concurrency.

I think this is a great general rule. Any one of these things is a reason to tread lightly. All of them at once? Here be dragons.