Hi, i have some problems with a new version
Here we are..
[15:00:51] Userfile loaded, unpacking...
[15:00:56] * Last context: tclhash.c/710 [Tcl proc: *raw:irc:315, param: $_raw1 $_raw2 $_raw3]
[15:00:56] * Please REPORT this BUG!
[15:00:56] * Check doc/BUG-REPORT on how to do so.
[15:00:56] * Wrote DEBUG
[15:00:56] * SEGMENT VIOLATION -- CRASHING!
I'm trying with make debug already but the problem is same.
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.
eggdrop debug
eggdrop debug
On a unix system everything is a file ; if something is not a file , it is a proccess.
same [censored] 
different day
[22:03:07] CTCP DCC: CHAT chat 1835584260 1024 from k (kiril@kiril.FreeBSD.org)
[22:03:07] DCC connection: CHAT (Kiril!kiril@kiril.FreeBSD.org)
[22:03:12] Logged in: Kiril (kiril@kiril.FreeBSD.org/1024)
[22:03:12] * Last context: tclhash.c/710 [Tcl proc: *chon:console:chon, param: $_chonof1 $_chonof2]
[22:03:12] * Please REPORT this BUG!
[22:03:12] * Check doc/BUG-REPORT on how to do so.
[22:03:12] * Wrote DEBUG
[22:03:12] * SEGMENT VIOLATION -- CRASHING!
So, i have a templorary solution.
When i compile official eggdrop version (1.6.20) i have no problem, but when i'm put a patch for ssl and problems comes like a rain
different day[22:03:07] CTCP DCC: CHAT chat 1835584260 1024 from k (kiril@kiril.FreeBSD.org)
[22:03:07] DCC connection: CHAT (Kiril!kiril@kiril.FreeBSD.org)
[22:03:12] Logged in: Kiril (kiril@kiril.FreeBSD.org/1024)
[22:03:12] * Last context: tclhash.c/710 [Tcl proc: *chon:console:chon, param: $_chonof1 $_chonof2]
[22:03:12] * Please REPORT this BUG!
[22:03:12] * Check doc/BUG-REPORT on how to do so.
[22:03:12] * Wrote DEBUG
[22:03:12] * SEGMENT VIOLATION -- CRASHING!
So, i have a templorary solution.
When i compile official eggdrop version (1.6.20) i have no problem, but when i'm put a patch for ssl and problems comes like a rain
On a unix system everything is a file ; if something is not a file , it is a proccess.
pseudo wrote:Please recompile with make debug and provide a full backtrace, as adviced in doc/BUG-REPORT. We need a backtrace in order to find the problem, since the DEBUG file is not useful by itself.
I was asking you for a full gdb backtrace, in order to figure out what's your problem. Make debug is to make the debug information more useful, did you actually thought it will fix your bot?Arkadietz wrote:same [censored] Smile different day
[22:03:07] CTCP DCC: CHAT chat 1835584260 1024 from k (kiril@kiril.FreeBSD.org)
[22:03:07] DCC connection: CHAT (Kiril!kiril@kiril.FreeBSD.org)
[22:03:12] Logged in: Kiril (kiril@kiril.FreeBSD.org/1024)
[22:03:12] * Last context: tclhash.c/710 [Tcl proc: *chon:console:chon, param: $_chonof1 $_chonof2]
[22:03:12] * Please REPORT this BUG!
[22:03:12] * Check doc/BUG-REPORT on how to do so.
[22:03:12] * Wrote DEBUG
[22:03:12] * SEGMENT VIOLATION -- CRASHING!
Although you didn't provide any useful information, I can guess what's your problem. You're using the unofficial, unsupported and buggy SSL patch, which has already two serious problems and that one is the third.Arkadietz wrote:[22:03:12] * Last context: tclhash.c/710 [Tcl proc: *chon:console:chon, param: $_chonof1 $_chonof2]
It shifts down the module symbols lookup table in src/modules.c, without updating properly the corresponding definitions in src/mod/module.h, so instead of the console_chon function, a completely different one is called, which logically leads to a crash.
The patch is very buggy and obviously the author didn't bother to test it. Here are the other problems, I've found so far (we find a new one almost every day): It's the patch author's job to fix these problems and do his homework before submitting patches. All of these should have been obvious at the moment of writing the patch.