I said [EMAIL PROTECTED], but that's OK; the stack trace shows that the problem is that your ircd.conf is incorrect. Please review and correct your C-lines. Sorry that there isn't a better diagnostic message for the problem; the configuration file subsystem is way overdue for roto-tilling.
> (gdb) backtrace > #0 match (mask=0x0, string=0x8143843 "Cleveland-r.Oh.US.partynet.org") at > match.c:170 > #1 0x806eca3 in attach_confs_byname (cptr=0x8143800, > name=0x8143843 "Cleveland-r.Oh.US.partynet.org", statmask=53248) at > s_conf.c:700 > #2 0x80706d6 in conf_check_server (cptr=0x8143800) at s_conf.c:1621 > #3 0x805e2af in mr_server (cptr=0x8143800, sptr=0x8143800, parc=8, > parv=0x8124520) at m_server.c:311 > #4 0x8068d26 in parse_client (cptr=0x8143800, buffer=0x81439a1 "SERVER", > bufend=0x8143a0d "") > at parse.c:916 > #5 0x8068663 in client_dopacket (cptr=0x8143800, length=108) at packet.c:123 > #6 0x806d52e in read_packet (cptr=0x8143800, socket_ready=65) at s_bsd.c:725 > #7 0x806dbe4 in read_message (delay=60) at s_bsd.c:1044 > #8 0x8051153 in main (argc=0, argv=0xbfbffbb4) at ircd.c:735 > #9 0x8049639 in _start () -- Kevin L. Mitchell <[EMAIL PROTECTED]>
