> Beside that you cannot simply trap on the `lock' prefix it is of
> course completely wrong that `lock' isn't used on user-level. glibc
> plus its other libraries use it quite often to handle concurrency.
Anyway, if you can trap it, you can then check if the opcode is bad - if
not, return. It'll be a minor (?) performance hit though..
_____________________________________________________________________
/ __// /__ ____ __ Erkki Seppälä\ \
/ /_ / // // /\ \/ / Inside Informatics ry \ /
/_/ /_/ \___/ /_/\_\@inside.org http://www.inside.org/~flux/ \/