This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.


For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.

Crash on .status

General support and discussion of Eggdrop bots.
Post Reply
L
Luminous
Op
Posts: 146
Joined: Fri Feb 12, 2010 1:00 pm

Crash on .status

Post by Luminous »

Any idea what could cause this? i have a hunch that it is the ssl+thread support patch, as the last bot I compiled did not have the patch or this issue:
#me# status
* Last context: tclhash.c/684 [Tcl proc: *dcc:status, param: $_dcc1 $_dcc2 $_dcc3]
* Please REPORT this BUG!
* Check doc/BUG-REPORT on how to do so.
* Wrote DEBUG
* SEGMENT VIOLATION -- CRASHING!
And yeah, I will report it...
n
nml375
Revered One
Posts: 2860
Joined: Fri Aug 04, 2006 2:09 pm

Post by nml375 »

Unfortunately, this limited information doesn't shed much light on the issue/bug. There are a few IPv6-patches out there with known bugs causing segment violations, though most ssl-patches are "clean".

The content of the DEBUG file as well as a complete backtrace (see BUG-REPORT for further details) might help pinning down the issue.
NML_375
L
Luminous
Op
Posts: 146
Joined: Fri Feb 12, 2010 1:00 pm

Post by Luminous »

I didn't see the DEBUG file before, its below. What do you mean by "complete backtrace"? I looked in BUG-REPORT and its just a guideline for bug reports, but I don't see anything about that.
debug (eggdrop v1.6.19+ctcpfix) written Thu Jul 8 12:57:43 2010
Full Patch List: SSL ctcpfix
Tcl library: /usr/share/tcltk/tcl8.5
Tcl version: 8.5.8 (header version 8.5.8)
Tcl is threaded
Compile flags: gcc -pipe -g -O2 -Wall -I.. -I.. -DHAVE_CONFIG_H
Link flags: gcc -pipe
Strip flags: touch
Context: tclhash.c/684, [Tcl proc: *raw:PRIVMSG, param: $_raw1 $_raw2 $_raw3]
tclhash.c/695, []
tclhash.c/680, []
tclhash.c/684, [Tcl proc: *raw:irc:msg, param: $_raw1 $_raw2 $_raw3]
tclhash.c/695, []
tclhash.c/680, []
tclhash.c/684, [Tcl proc: *raw:PRIVMSG, param: $_raw1 $_raw2 $_raw3]
tclhash.c/695, []
tclhash.c/680, []
tclhash.c/684, [Tcl proc: *dcc:console, param: $_dcc1 $_dcc2 $_dcc3]
tclhash.c/695, []
tclhash.c/680, []
tclhash.c/684, [Tcl proc: *dcc:console, param: $_dcc1 $_dcc2 $_dcc3]
tclhash.c/695, []
tclhash.c/680, []
tclhash.c/684 [Tcl proc: *dcc:status, param: $_dcc1 $_dcc2 $_dcc3]

SOCK ADDR PORT NICK HOST TYPE
---- -------- ----- --------- ----------------- ----
7 D049D96B 64955 (telnet) * lstn 64955
8 D8A5BF34 6667 (server) irc.freenode.net serv (lag: 0)
10 CFC0476B 54425 Nebulae bnc1.shellium.org chat flags: cpTEp/0
26 47FFB591 54001 jack .east.verizon.net chat flags: cPtep/0

Compiled without extensive memory debugging (sorry).
Open sockets: 7 (listen), 8, 10, 26, 9 (file), done.
n
nml375
Revered One
Posts: 2860
Joined: Fri Aug 04, 2006 2:09 pm

Post by nml375 »

4.8 ) If the bot dumped a 'core' file when it crashed, it would be *very* useful if you could paste gdb's output during the following steps:
First call gdb

Code: Select all

$ gdb eggdrop -c core
and then enter 'bt' on gdb's command line:

Code: Select all

(gdb) bt
Keep your core file for at least one week, so that the dev team can ask for further information if needed. However, don't send us the core file unless we ask for it.

NOTE: If this is a bug you can reproduce, please compile with make debug and follow the above step. It can greatly help find and fix the bug.
I suppose I should've mentioned that "bt" is an acronym for "backtrace". Sorry for that.

If your system has disabled "coredumping" by default, try this before starting your eggdrop:

Code: Select all

ulimit -c 10000
The syntax for ulimit may vary with different shells and systems, "if in doubt - check the manpages".
NML_375
Post Reply