Somewhere, probably in the resolve code, is something that makes eggdrops later than 1.6.1 die horribly on /dcc chat eggie.
I'm using a Windows DNS server on a remote machine, I bet that's it, but eggie shouldn't die from it. The actual message from various versions point to a line in server.c but it makes no sense, probably due to macro expansion. For what it's worth, here's the error:
[00:32] Timeout/EOF ident connection
[00:32] * Last context: server:server.c/1395 []
[00:32] * Please REPORT this BUG!
[00:32] * Check doc/BUG-REPORT on how to do so.
[00:32] * Wrote DEBUG
[00:32] * SEGMENT VIOLATION -- CRASHING!
And just to be cool it also dies on +host DCC commands (I could dcc to it through a reverse DCC command within a script):
[01:09] #Micke# +host Konstiga_ *!konstiga_e@*.hs.bonet.se
[01:09] * Last context: tclhash.c/677 [Tcl proc: *dcc:+host, param: $_dcc1 $_dcc2 $_dcc3]
[01:09] * Please REPORT this BUG!
[01:09] * Check doc/BUG-REPORT on how to do so.
[01:09] * Wrote DEBUG
[01:09] * SEGMENT VIOLATION -- CRASHING!
Did I do the mistake of thinking older linux work work, that windows DNS servers would work or is there something else I could change? I have NO intention of going through 4 hours of registering pain JUST to let someone know about this bug, so this is it. Maybe the eggdrop peaked at 1.6.1 (I've tried 1.6.7, 1.6.10 - both dies on these things while 1.6.1 works perfectly).
Btw, linux version is 2.2.16-22, gotten from redhat something a while back.
/Micke