[01:06:58] --- dev-zero@jabber.org has become available [04:53:03] --- dev-zero@jabber.org has left [05:51:15] --- shadow@gmail.com/owl865F0E65 has become available [05:55:34] --- dev-zero@jabber.org has become available [06:42:14] --- dev-zero@jabber.org has left [08:42:50] --- SecureEndpoints has become available [10:25:19] --- Russ has become available [10:47:27] --- matt has become available [12:38:33] --- manfred furuholmen has become available [12:45:40] --- manfred furuholmen has left [15:59:21] --- matt has left [16:30:07] --- Russ has left: Disconnected [16:35:32] --- matt has become available [16:54:25] --- Simon Wilkinson has left [17:03:19] --- matt has left [17:06:44] --- Russ has become available [20:12:46] --- matt has become available [20:15:56] q: reported lock hierarchy violation traps w/ vanilla oafsw 1.5.55? [20:40:35] using a checked build. what's the question? [20:44:12] btw, the acronym is "oafw" [20:47:46] the lock violation is an impossibility. in order for the assertion to fail the thread that is holding the lock must not have been holding the lock at the time the thread released the lock in a previous pass through the loop [20:49:39] the assertion is only triggered on that one smb lock. if you see something wrong with the logic in the code, feel free to point it out. [22:43:55] head and 1_5_x build on windows again.