Critical: .\socket.c:640: REQUIRE(sock->hEvent != ((void *)0)) failed, general: critical: exiting (due to assertion failure)

[Ian Tait]

Hi,

I'll try that again, as outlook got a bit quick on the mark,

On a windows 2000 machine, with the latest beta, I get 

.\socket.c:640: REQUIRE(sock->hEvent != ((void *)0)) failed 

and then 'exiting (due to assertion failure)

Just FYI.

Thanks,

Ian

> -----Original Message-----
> From: Ian Tait 
> Sent: 24 July 2008 10:56
> To: comp-protocols-dns-bind at isc.org
> Subject: RE: Critical: .\socket.c:640: REQUIRE(sock->hEvent 
> != ((void *)0)) failed, general: critical: exiting (due to 
> assertion failure)
> 
> Hi,
> 
> On a windows 2000 machine with the latest 9.5  
> 
> 
> 
> 
> > -----Original Message-----
> > From: bind-users-bounce at isc.org
> > [mailto:bind-users-bounce at isc.org] On Behalf Of Danny Mayer
> > Sent: 23 June 2008 05:16
> > To: Fabien V.
> > Cc: comp-protocols-dns-bind at isc.org
> > Subject: Re: Critical: .\socket.c:640: REQUIRE(sock->hEvent 
> != ((void 
> > *)0)) failed, general: critical: exiting (due to assertion failure)
> > 
> > Fabien V. wrote:
> > > Hi,
> > > 
> > > I have Bind 9.5 for Windows XP.
> > > 
> > > Sometimes, I have the following error occurred :
> > > 
> > > general: critical: .\socket.c:640: REQUIRE(sock->hEvent != ((void
> > > *)0)) failed
> > > general: critical: exiting (due to assertion failure).
> > > 
> > > Can I help from anyone ?
> > > 
> > > Thank you very much and see you soon.
> > > 
> > > Fabien V.
> > 
> > This is the second report that I have seen on this. Do you have any 
> > dumps or have anything else in the event log? If so can you 
> send this 
> > directly to me (and not via the newsgroup)?
> > Which version of Windows XP service pack are you running? 
> Do you have 
> > logs of what was happening when this was triggered?
> > Was this after a AXFR transfer?
> > 
> > I have been working on fixing this.
> > 
> > Danny
> > 
> >