`
Question one: Please describe your computer system
Hardware type?
Operating System? (try uname -a for most, or uname -X for SCO)
Your compiler (include version, if known)
What scripts/script packs you run (phoenix, uus, superpack, etc)
Anything else you think might be helpful.
Hardware: Pentium P5 200mhz, 64m ram (standard Dell Dimension
M200a Hardware)
OS: FreeBSD 4.4-STABLE
Compiler: GCC 2.95.3
Scripts: n/a
Question two: Where does your problem occur?
[ ] Configure time (dies while running configure)
[ ] Compiler time (dies when you type 'make')
[ ] Run time (You got a "CRITICAL PROTECTION ERROR")
[ ] Run time (You got a "PANIC" message)
[ ] Run time (non-fatal logic bug)
[X] Run time (fatal logic error)
If it is at run time, please try to describe as best you can what
you were doing when the client malfunctioned. Had you just run
a command? Can you duplicate the error? What seems to cause the
error in your best judgement? Have you found anything else
that independantly causes this same problem?
This error was totally out of the blue, I've been using epic for about 3
months now and have never seen it. Pasted below is the text that
appeared when the error occurred:
------------------------------------------------------------------------
-----
An unrecoverable logic error has occured.
Please fill out the BUG_FORM file, and include the following message:
Panic: [EPIC4-1.0:Referential integrity failure: Channel [#freebsd] on
server [1
] is connected to window [3] on server [0]]
Call stack
End of call stack
Abort trap (core dumped)
------------------------------------------------------------------------
-----
If you know how to use a debugger, it would be helpful if you
can get a stack trace, and cut and paste it here.
------------------------------------------------------------------------
-----
(gdb) bt
#0 0x2818080c in kill () from /usr/lib/libc.so.4
#1 0x281bc85e in abort () from /usr/lib/libc.so.4
#2 0x80794ef in panic (
format=0x80a7e80 "Referential integrity failure: Channel [%s] on
server [%d] is connected to window [%d] on server [%d]")
at ircaux.c:1355
#3 0x8080e43 in channel_check_windows () at names.c:1892
#4 0x8099040 in window_check_channels () at window.c:2161
#5 0x808025f in destroy_server_channels (server=0) at names.c:1354
#6 0x808dbe7 in close_server (old=0,
message=0x8128e08 "EPIC Panic: EPIC4-1.0:Referential integrity
failure: Channel [#freebsd] on server [1] is connected to window [3] on
server [0]") at server.c:1322
#7 0x808d987 in reconnect (oldserv=0) at server.c:1201
#8 0x808dafd in close_all_servers (
message=0xbfbfa218 "EPIC Panic: EPIC4-1.0:Referential integrity
failure: Channel [#freebsd] on server [1] is connected to window [3] on
server [0]") at server.c:1287
#9 0x807683f in irc_exit (really_quit=1, format=0x80a64b7 "EPIC Panic:
%s:%s") at ./irc.c:279
#10 0x807959c in beep_em (beeps=134905472) at ircaux.c:1375
#11 0x8080e43 in channel_check_windows () at names.c:1892
#12 0x8099040 in window_check_channels () at window.c:2161
#13 0x8077654 in io (what=0x80a6134 "main") at ./irc.c:908
#14 0x8077c15 in main (argc=1, argv=0xbfbffbcc) at ./irc.c:1262
#15 0x804a4e5 in _start ()
------------------------------------------------------------------------
-----
Please include any other information that you think we should know
about.
Thank you for taking the time to fill this out. We hope that this form
will make finding and fixing bugs much less of a headache for both
us and you. We will reply to you as soon as possible (probably the next
school day), and we will let you know when we've fixed the problem and
give you a patch for it.
Author(s): Originally by Michael Sandroff,
Current copyright holder is Matthew Green
EPIC is developed by EPIC Software Labs for the EPIC project.
"EPIC" and "ESL" are trademarks of the EPIC project.
Product: ircII-EPIC4pre2 (see UPDATES)
<EOF>
_______________________________________________
List mailing list
[EMAIL PROTECTED]
http://epicsol.org/mailman/listinfo/list
