From owner-freebsd-threads@FreeBSD.ORG Fri Jul 20 16:29:01 2012 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BBE37106566C; Fri, 20 Jul 2012 16:29:01 +0000 (UTC) (envelope-from freebsdml@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) by mx1.freebsd.org (Postfix) with ESMTP id 873B18FC1A; Fri, 20 Jul 2012 16:29:01 +0000 (UTC) Received: from [192.168.0.225] (atoulouse-256-1-140-121.w90-45.abo.wanadoo.fr [90.45.187.121]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id B323D43B91; Fri, 20 Jul 2012 11:28:53 -0500 (CDT) Message-ID: <5009873C.4080709@marino.st> Date: Fri, 20 Jul 2012 18:28:44 +0200 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20120129 Thunderbird/10.0 MIME-Version: 1.0 To: Alfred Perlstein References: <500854EC.3040305@marino.st> <20120719212326.GN98608@elvis.mu.org> <50090FB9.6050606@marino.st> <20120720150803.GS98608@elvis.mu.org> In-Reply-To: <20120720150803.GS98608@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-threads@freebsd.org Subject: Re: Fingerpointing about broken Ada tasking starting with FreeBSD 9.0 threading X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jul 2012 16:29:01 -0000 On 7/20/2012 17:08, Alfred Perlstein wrote: > > There is no big picture unless you take the time to diagnose what > is happening. There is a bug somewhere. Talking about "big > picture" doesn't mean anything. > > The bug could be due to any of the reasons you described, or due > to other reasons. What needs to be done is some investigation into > what is triggering the bug and then determine if it's a bug, false > positive, corruption or something else. I agree, and I'll try. What I was trying to get at is *if* the problem really is with FreeBSD, there should be more than just me looking into it given the implications of what that would mean. The worst case scenario is that this is 100% a FreeBSD problem, and that would have some fallout. In my previous work, we had to map out every possibility and plan for it -- we didn't have the luxury of determining the fault and then coming up with a plan. That mentality is carrying over probably. > > It sounds like you're advocating for just removing an assertion without > proving it's a false positive. I don't think that will work out unfortunately. > Not at all, but there was a serious consequence of this assertion and it's not a pre-production assertion either. I don't have any preconceived notion of the cause of the fault nor the solution. My mind is wide open at this point. John