On my bots which are running in channels > 800 users i got this bug:
compiled without extensive memory debugging in combination with scripts that are monitoring pub - *
Can anybody tell me how to fix this?
thanks
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.
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.
got bug "compiled without extensive memory debugging&qu
The information you have supplied is very limiting to say the least.
The message "Compiled without excessive memory debugging" means what it says. It's not an error, it's an informative message.
When the bot is comiled with this setting (by using "make debug" in placment of the single "make" command), the bot will track memory, whenever it is allocated. This is used, to see places where memory is used, but is not returned, and will expose (to the experienced user) places where things need to be fixed.
If you bot is crashing, we will need alittle more information.
What scripts are you using? Yes, these are important, it will help us fineout, if the problem is caused by a script, and maybe which one.
Did the bot actualy crash? This message is displayed in other places apart from crash information. It would be helpfult o to know where the message was dispalyed, and is possible how you got it to display.
If the bot did crash. Can you paste the content of the DEBUG file located in you eggdrop directory? This file will store ifnormation about the last crash, unless the crash was that serious, that it wasn't able to do this. If it was unable, then you should try and be ont he partyline during a crash, and paste the last 10 lines, so we can see where the crash occured.
These questiosn are only a starting point, and would most likely lead to more complex question, based on the answers provided.
The message "Compiled without excessive memory debugging" means what it says. It's not an error, it's an informative message.
When the bot is comiled with this setting (by using "make debug" in placment of the single "make" command), the bot will track memory, whenever it is allocated. This is used, to see places where memory is used, but is not returned, and will expose (to the experienced user) places where things need to be fixed.
If you bot is crashing, we will need alittle more information.
What scripts are you using? Yes, these are important, it will help us fineout, if the problem is caused by a script, and maybe which one.
Did the bot actualy crash? This message is displayed in other places apart from crash information. It would be helpfult o to know where the message was dispalyed, and is possible how you got it to display.
If the bot did crash. Can you paste the content of the DEBUG file located in you eggdrop directory? This file will store ifnormation about the last crash, unless the crash was that serious, that it wasn't able to do this. If it was unable, then you should try and be ont he partyline during a crash, and paste the last 10 lines, so we can see where the crash occured.
These questiosn are only a starting point, and would most likely lead to more complex question, based on the answers provided.
-
mmB-
debug context
Debug (eggdrop v1.6.10) written Mon Nov 25 22:25:29 2002
Full Patch List:
Tcl library: /usr/lib/tcl8.3
Tcl version: 8.3.3 (header version 8.3.3)
Compile flags: gcc -pipe -g -O2 -Wall -I.. -I.. -DHAVE_CONFIG_H
Link flags: gcc -pipe
Strip flags: strip
Context: tclhash.c/677, [Tcl proc: <null>, param: $_raw1 $_raw2 $_raw3]
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: handle_lamer, param: $_raw1 $_raw2 $_raw3]
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: *raw:irc:msg, param: $_raw1 $_raw2 $_raw3]
tclhash.c/673, []
tclhash.c/677, [Tcl proc: advert:check, param: $_pubm1 $_pubm2 $_pubm3 $_pubm4 $_pubm5]
tclhash.c/681, []
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: *raw:PRIVMSG, param: $_raw1 $_raw2 $_raw3]
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677 [Tcl proc: handle_lamer, param: $_raw1 $_raw2 $_raw3]
SOCK ADDR PORT NICK HOST TYPE
---- -------- ----- --------- ----------------- ----
9 D5DDBD01 6667 (server) c.de.quakenet.org serv (lag: 0)
4 D9A05A63 6009 (telnet) * lstn 6009
3 00000000 0 (dns) dns (ready)
Compiled without extensive memory debugging (sorry).
Open sockets: 3 (passed on), 4 (listen), 9, 10 (file), done.
Full Patch List:
Tcl library: /usr/lib/tcl8.3
Tcl version: 8.3.3 (header version 8.3.3)
Compile flags: gcc -pipe -g -O2 -Wall -I.. -I.. -DHAVE_CONFIG_H
Link flags: gcc -pipe
Strip flags: strip
Context: tclhash.c/677, [Tcl proc: <null>, param: $_raw1 $_raw2 $_raw3]
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: handle_lamer, param: $_raw1 $_raw2 $_raw3]
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: *raw:irc:msg, param: $_raw1 $_raw2 $_raw3]
tclhash.c/673, []
tclhash.c/677, [Tcl proc: advert:check, param: $_pubm1 $_pubm2 $_pubm3 $_pubm4 $_pubm5]
tclhash.c/681, []
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: *raw:PRIVMSG, param: $_raw1 $_raw2 $_raw3]
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677 [Tcl proc: handle_lamer, param: $_raw1 $_raw2 $_raw3]
SOCK ADDR PORT NICK HOST TYPE
---- -------- ----- --------- ----------------- ----
9 D5DDBD01 6667 (server) c.de.quakenet.org serv (lag: 0)
4 D9A05A63 6009 (telnet) * lstn 6009
3 00000000 0 (dns) dns (ready)
Compiled without extensive memory debugging (sorry).
Open sockets: 3 (passed on), 4 (listen), 9, 10 (file), done.
-
mmB-
Unfortunately I think you are mistaken .. making a debug version of the bot only means that you may get more info when the bot crashes again. It shouldnt fix anything having a debug build of the bot.
However, whichever script that contains the proc handle_lamer, will once again crash your bot someday - almost guaranteed.
However, whichever script that contains the proc handle_lamer, will once again crash your bot someday - almost guaranteed.
-
mmB-
today i got this: 
Debug (eggdrop v1.6.13) written Tue Nov 26 21:49:01 2002
Full Patch List:
Tcl library: /usr/lib/tcl8.3
Tcl version: 8.3.3 (header version 8.3.3)
Compile flags: gcc -pipe -g -O2 -Wall -I.. -I.. -DHAVE_CONFIG_H -g3 -DDEBUG_ASSERT -DDEBUG_MEM
Link flags: gcc -pipe -g
Strip flags: touch
Context: tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: *raw:irc:join, param: $_raw1 $_raw2 $_raw3]
tclhash.c/673, []
tclhash.c/677, [Tcl proc: do_auth, param: $_jp1 $_jp2 $_jp3 $_jp4]
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: peak:join, param: $_jp1 $_jp2 $_jp3 $_jp4]
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: *join:notes, param: $_jp1 $_jp2 $_jp3 $_jp4]
tclhash.c/681, []
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: <null>, param: $_raw1 $_raw2 $_raw3]
tclhash.c/681 []
SOCK ADDR PORT NICK HOST TYPE
---- -------- ----- --------- ----------------- ----
3 00000000 0 (dns) dns (ready)
4 D9A05A63 6005 (telnet) * lstn 6005
7 3E1A7B07 6667 (server) c.de.quakenet.org serv (lag: 0)
File 'language.c' accounted for 15579/15579 (ok)
File 'chanprog.c' accounted for 689/689 (ok)
File 'misc.c ' accounted for 6911/6911 (ok)
File 'userrec.c ' accounted for 1545/1545 (ok)
File 'net.c ' accounted for 0/0 (ok)
File 'dccutil.c ' accounted for 126240/126240 (ok)
File 'botnet.c ' accounted for 4600/4600 (ok)
File 'tcl.c ' accounted for 4920/4920 (ok)
File 'tclhash.c ' accounted for 23006/23006 (ok)
File 'tclmisc.c ' accounted for 14/14 (ok)
File 'modules.c ' accounted for 933/933 (ok)
File 'tcldcc.c ' accounted for 12/12 (ok)
File 'dns.c ' accounted for 0/0 (ok)
Module 'encryption' accounted for 0/0 (ok)
Module 'transfer ' accounted for 0/0 (ok)
Module 'share ' accounted for 36/36 (ok)
Module 'console ' accounted for 0/0 (ok)
Module 'notes ' accounted for 0/0 (ok)
Module 'irc ' accounted for 0/0 (ok)
Module 'ctcp ' accounted for 0/0 (ok)
Module 'server ' accounted for 241/998 (debug follows:)
server.c /951 :(0014) server.c /968 :(0014) servmsg.c /271 :(001F)
server.c /879 :(0041) server.c /879 :(0041) server.c /879 :(0045)
server.c /879 :(0040) server.c /865 :(000C) server.c /865 :(000C)
server.c /879 :(0051) server.c /865 :(000C) server.c /879 :(003F)
server.c /865 :(000C) server.c /865 :(000C) server.c /865 :(000C)
server.c /879 :(003D) server.c /865 :(000C) server.c /879 :(0039)
server.c /865 :(000C) server.c /865 :(000C) server.c /879 :(0041)
server.c /879 :(0041) server.c /865 :(000C) server.c /879 :(0041)
server.c /879 :(003F) server.c /865 :(000C) server.c /865 :(000C)
Module 'channels ' accounted for 278213/278213 (ok)
Module 'dns ' accounted for 0/0 (ok)
Module 'eggdrop ' accounted for 0/0 (ok)
--- End of debug memory list.
Open sockets: 3 (passed on), 4 (listen), 7, 8 (file), done.
Debug (eggdrop v1.6.13) written Tue Nov 26 21:49:01 2002
Full Patch List:
Tcl library: /usr/lib/tcl8.3
Tcl version: 8.3.3 (header version 8.3.3)
Compile flags: gcc -pipe -g -O2 -Wall -I.. -I.. -DHAVE_CONFIG_H -g3 -DDEBUG_ASSERT -DDEBUG_MEM
Link flags: gcc -pipe -g
Strip flags: touch
Context: tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: *raw:irc:join, param: $_raw1 $_raw2 $_raw3]
tclhash.c/673, []
tclhash.c/677, [Tcl proc: do_auth, param: $_jp1 $_jp2 $_jp3 $_jp4]
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: peak:join, param: $_jp1 $_jp2 $_jp3 $_jp4]
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: *join:notes, param: $_jp1 $_jp2 $_jp3 $_jp4]
tclhash.c/681, []
tclhash.c/681, []
tclhash.c/673, []
tclhash.c/677, [Tcl proc: <null>, param: $_raw1 $_raw2 $_raw3]
tclhash.c/681 []
SOCK ADDR PORT NICK HOST TYPE
---- -------- ----- --------- ----------------- ----
3 00000000 0 (dns) dns (ready)
4 D9A05A63 6005 (telnet) * lstn 6005
7 3E1A7B07 6667 (server) c.de.quakenet.org serv (lag: 0)
File 'language.c' accounted for 15579/15579 (ok)
File 'chanprog.c' accounted for 689/689 (ok)
File 'misc.c ' accounted for 6911/6911 (ok)
File 'userrec.c ' accounted for 1545/1545 (ok)
File 'net.c ' accounted for 0/0 (ok)
File 'dccutil.c ' accounted for 126240/126240 (ok)
File 'botnet.c ' accounted for 4600/4600 (ok)
File 'tcl.c ' accounted for 4920/4920 (ok)
File 'tclhash.c ' accounted for 23006/23006 (ok)
File 'tclmisc.c ' accounted for 14/14 (ok)
File 'modules.c ' accounted for 933/933 (ok)
File 'tcldcc.c ' accounted for 12/12 (ok)
File 'dns.c ' accounted for 0/0 (ok)
Module 'encryption' accounted for 0/0 (ok)
Module 'transfer ' accounted for 0/0 (ok)
Module 'share ' accounted for 36/36 (ok)
Module 'console ' accounted for 0/0 (ok)
Module 'notes ' accounted for 0/0 (ok)
Module 'irc ' accounted for 0/0 (ok)
Module 'ctcp ' accounted for 0/0 (ok)
Module 'server ' accounted for 241/998 (debug follows:)
server.c /951 :(0014) server.c /968 :(0014) servmsg.c /271 :(001F)
server.c /879 :(0041) server.c /879 :(0041) server.c /879 :(0045)
server.c /879 :(0040) server.c /865 :(000C) server.c /865 :(000C)
server.c /879 :(0051) server.c /865 :(000C) server.c /879 :(003F)
server.c /865 :(000C) server.c /865 :(000C) server.c /865 :(000C)
server.c /879 :(003D) server.c /865 :(000C) server.c /879 :(0039)
server.c /865 :(000C) server.c /865 :(000C) server.c /879 :(0041)
server.c /879 :(0041) server.c /865 :(000C) server.c /879 :(0041)
server.c /879 :(003F) server.c /865 :(000C) server.c /865 :(000C)
Module 'channels ' accounted for 278213/278213 (ok)
Module 'dns ' accounted for 0/0 (ok)
Module 'eggdrop ' accounted for 0/0 (ok)
--- End of debug memory list.
Open sockets: 3 (passed on), 4 (listen), 7, 8 (file), done.
Again. not much to say except that one of your scripts has a bad error in it. Its not an eggdrop bug, if that is what you are expecting, and I cant magically fix it either if that is what you are expecting.
You gonna have to either remove scripts until it goes away, or start debugging scripts - I suggest you start with the one I mentioned before that crashed it last time. This time I cant even tell you which tcl proc it crashed in, seeing as it didnt have the name.
You gonna have to either remove scripts until it goes away, or start debugging scripts - I suggest you start with the one I mentioned before that crashed it last time. This time I cant even tell you which tcl proc it crashed in, seeing as it didnt have the name.
-
mmB-