On Sat, Jul 27, 2013 at 10:33:18AM +0200, Dominic Fandrey wrote:
On 26/07/2013 19:10, Dominic Fandrey wrote:
On 25/07/2013 12:00, Konstantin Belousov wrote:
On Thu, Jul 25, 2013 at 09:56:59AM +0200, Dominic Fandrey wrote:
On 22/07/2013 12:07, Konstantin Belousov wrote:
On Mon, Jul 22,
On Sat, Jul 27, 2013 at 03:13:05PM -0700, Michael Tratz wrote:
Let's assume the pid which started the deadlock is 14001 (it will be a
different pid when we get the results, because the machine has been restarted)
I type:
show proc 14001
I get the thread numbers from that output and
On 28/07/2013 08:24, Konstantin Belousov wrote:
On Sat, Jul 27, 2013 at 10:33:18AM +0200, Dominic Fandrey wrote:
On 26/07/2013 19:10, Dominic Fandrey wrote:
On 25/07/2013 12:00, Konstantin Belousov wrote:
On Thu, Jul 25, 2013 at 09:56:59AM +0200, Dominic Fandrey wrote:
On 22/07/2013 12:07,
On 28/07/2013 08:24, Konstantin Belousov wrote:
On Sat, Jul 27, 2013 at 10:33:18AM +0200, Dominic Fandrey wrote:
On 26/07/2013 19:10, Dominic Fandrey wrote:
On 25/07/2013 12:00, Konstantin Belousov wrote:
On Thu, Jul 25, 2013 at 09:56:59AM +0200, Dominic Fandrey wrote:
On 22/07/2013
The issue reported here:
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2013-07/msg00179.html
is still present in FreeBSD 9.2-PRE, although it seemingly has been
resolved in CURRENT. I run into this problem again on 9.2-PRE with a
port that relies on strictness in C++11 conformity in
