Bind 9.5.1b1exiting (due to assertion failure)

[Fr34k]

I have core from Solaris9 SPARC running version: 9.5.1b1
Questions:
    Is there a fix for this version?
    Do you want the core file (or any details about it). If so, contact me off list with instructions.
Let me know
Thank you



----- Original Message ----
From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya at isc.org>
To: Alan Clegg <Alan_Clegg at isc.org>
Cc: bind-users at isc.org
Sent: Wednesday, July 23, 2008 2:59:59 PM
Subject: Re: Bind 9.5.1b1exiting (due to assertion failure)

At Wed, 23 Jul 2008 06:50:42 -0400,
Alan Clegg <Alan_Clegg at isc.org> wrote:

> >> We've heard this failure from others.  I've been thinking about it,
> >> but could not yet come up with an idea of how that can happen (much
> >> less how to fix it).
> > 
> > Same problem here, running bind 9.4.3b2 on Solaris 9.
> > 
> > 23-Jul-2008 08:52:44.906 general: resolver.c:5494: REQUIRE((((query) != 
> > 0) && (((const isc__magic_t *)(query))->magic == ((('Q') << 24 | ('!') 
> > << 16 | ('!') << 8 | ('!')))))) failed
> > 23-Jul-2008 08:52:44.906 general: exiting (due to assertion failure)
> 
> At this time, ISC is recommending that everyone stay within their branch
> and move to the -P1 releases (ie, if you are at 9.3.x, move to 9.3.5-P1,
> 9.4.x users should move to 9.4.2-P1).
> 
> Unless you have a definitive need to run the beta code, please remain
> with the -P1 releases to reduce the number of changes that are being
> introduced into your environment.

This is all completely true.  On top of that principle:

we'd still very much welcome beta version testers.  Regarding this
crash, we've noticed it and chased it, but have not yet identified how
that could happen.  Without a core it's unlikely we can debug it
further, and even if we have one, I suspect it's not very informative
due to the nature of this bug (it should have been happened at an
earlier stage of the code, and is just revealed at this point).

For those who are willing to help debug this crash: please apply the
patch available at:
http://www.jinmei.org/bind-9.4.3b2-dispatch.diff

it doesn't change the behavior and shouldn't do any more harm.  It
just adds some debug information we can examine when the crash
happens.  And please report the backtrace next time named crashes at
this point.

For those who are willing to help test beta but don't want to see this
crash: if you can live with the possibly decreased performance without
threads, please rebuild named without threads.  This is most likely an
inter-thread race, and shouldn't happen without threads.

Thanks,

---
JINMEI, Tatuya