Date: Fri, 20 Jul 2012 19:32:05 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: John Marino <freebsdml@marino.st> Cc: freebsd-threads@freebsd.org Subject: Re: Fingerpointing about broken Ada tasking starting with FreeBSD 9.0 threading Message-ID: <20120720163205.GR2676@deviant.kiev.zoral.com.ua> In-Reply-To: <5009873C.4080709@marino.st> References: <500854EC.3040305@marino.st> <20120719212326.GN98608@elvis.mu.org> <50090FB9.6050606@marino.st> <20120720150803.GS98608@elvis.mu.org> <5009873C.4080709@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
--SUcp5/vPb8ZOOFiR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 20, 2012 at 06:28:44PM +0200, John Marino wrote: > 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. >=20 > I agree, and I'll try. What I was trying to get at is *if* the problem= =20 > really is with FreeBSD, there should be more than just me looking into=20 > it given the implications of what that would mean. The worst case=20 > scenario is that this is 100% a FreeBSD problem, and that would have=20 > some fallout. In my previous work, we had to map out every possibility= =20 > and plan for it -- we didn't have the luxury of determining the fault=20 > and then coming up with a plan. That mentality is carrying over probably. >=20 > > > >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=20 > >unfortunately. > > >=20 > Not at all, but there was a serious consequence of this assertion and=20 > it's not a pre-production assertion either. I don't have any=20 > preconceived notion of the cause of the fault nor the solution. My mind= =20 > is wide open at this point. FYI, this problem is supposedly fixed by r238637, as much as I can judge based on your description and commit itself. --SUcp5/vPb8ZOOFiR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlAJiAUACgkQC3+MBN1Mb4j97QCg2nTw6N4wxx2M586I/+uvN31Y QGQAn3pHIIkcDTQEiTVx3HeeLHcgVxwo =3aun -----END PGP SIGNATURE----- --SUcp5/vPb8ZOOFiR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120720163205.GR2676>