On Tue, May 18, 2010 at 6:15 PM, Maddin, Peter <[email protected]> wrote: > Oh and thanks very much for everyone’s input.
It's an interesting one. I think if you'd been able to stack a complete callstack up until it blocked, you'd be able to see the security process halting it. I don't quite know how to do exactly that, but it would be interesting to see if it was visible that way. And then I'd suppose that would be an interesting/easy way of tracking down any lock-based error. > Very much appreciated. > > Regards Peter Maddin > Applications Development Officer > PathWest Laboratory Medicine WA > Phone : +618 9473 3944 > Fax : +618 9473 3982 > E-Mail : [email protected] > The contents of this e-mail transmission outside of the WAGHS network are > intended solely for the named recipient's), may be confidential, and may be > privileged or otherwise protected from disclosure in the public interest. > The use, reproduction, disclosure or distribution of the contents of this > e-mail transmission by any person other than the named recipient(s) is > prohibited. If you are not a named recipient please notify the sender > immediately. -- silky http://www.programmingbranch.com/
