Anope IRC Services

Anope Support => 1.8.x/1.7.x Support (Read Only) => Topic started by: Andrey on September 26, 2008, 09:12:26 PM

Title: [SOLVED] problem
Post by: Andrey on September 26, 2008, 09:12:26 PM
Anope: 1.7.21
InspIRCd: 1.1.21
OS: Debian Linux 2.6.9-023stab037.3-smp #1 SMP Wed Dec 13 19:33:33 MSK 2006 i686 GNU/Linux

" "

i deleted "text of the problem" for security.
Title: Re: InspIRCd + Anope problem
Post by: Jobe on September 26, 2008, 09:48:24 PM
Instead of asking, why not upgrade and find out. And yes it should have fixed it.
Title: Re: InspIRCd + Anope problem
Post by: Andrey on September 26, 2008, 09:58:59 PM
i'm asking, because in upgrade i losted few modules, and this forum its for discussion.
Title: Re: InspIRCd + Anope problem
Post by: Jobe on September 27, 2008, 02:45:04 AM
Depending on how you upgraded, you will have to recompile the modules too.

Using the same procedure you used to compile them to begin with.
Title: Re: InspIRCd + Anope problem
Post by: Jan Milants on September 27, 2008, 11:33:39 AM
he s probably referring to the modules that don't work yet on .22...

and your answer is in the .22 release notes..
Quote
In addition to that, a crashbug in ChanServ's ACCESS command has been fixed
Title: Re: InspIRCd + Anope problem
Post by: Andrey on September 27, 2008, 11:56:07 PM
i get same problem in .22, this problem is not fixed!  :'(
Title: Re: InspIRCd + Anope problem
Post by: Jan Milants on September 28, 2008, 11:41:41 AM
you were on IRC as well yet you have given us nothing actually usefull...
you say it crashes on ACCESS DEL, but it works just fine for everyone else. so chances are it s at your end.

I have asked you for a debug log of the crash and a backtrace (http://anope.info/wiki/Other:GDB) on IRC and got nothing.. unless you provide us with this there is nothing we can do.
and a /os modlist too ..
Title: Re: InspIRCd + Anope problem
Post by: Andrey on September 29, 2008, 10:21:20 AM
i get cookie problem for use paste page. i paste here.

#0  0x003c915a in strcasecmp () from /lib/tls/libc.so.6
#1  0x00631b29 in mEventAccessDel (argc=2, argv=0x9ea9718)
    at cs_access_notice.c:161
#2  0x080696ee in event_process_hook (name=0x91dd29 "access_del", argc=2,
    argv=0x9ea9718) at events.c:162
#3  0x0806a408 in send_event (name=0x91dd29 "access_del", argc=2)
    at events.c:55
#4  0x0091db02 in do_access (u=0x9ea14b8) at cs_access.c:370
#5  0x08065a73 in do_run_cmd (service=0x9aa19c0 "ChanServ", u=0x9ea14b8,
    c=0x9d11408, cmd=0xbff350ea "ACCESS") at commands.c:101
#6  0x080651d2 in chanserv (u=0x9ea14b8, buf=0xbff350ea "ACCESS")
    at chanserv.c:394
#7  0x0807420d in m_privmsg (source=0xbff35318 "tucupi",
    receiver=0xbff350e0 "ChanServ", msg=0xbff350ea "ACCESS") at messages.c:192
#8  0x00f0109b in anope_event_privmsg (source=0xbff35318 "tucupi", ac=2,
    av=0x48a240) at inspircd11.c:1517
#9  0x08083ac2 in process () at process.c:276
#10 0x08071db5 in main (ac=3, av=0xbff35444, envp=0xbff35454) at main.c:656

Thanks
Title: Re: InspIRCd + Anope problem
Post by: Andrey on September 29, 2008, 10:25:10 AM
modlist, i think one module cause this crashbug.

[06:23:28] -OperServ- Módulo: bs_seen [0.7.1] [3rd]
[06:23:28] -OperServ- Módulo: bs_noticeguest [$Id: bs_noticeguest.c v1.0.0 25-09-2006 n00bie $] [3rd]
[06:23:28] -OperServ- Módulo: bs_autoassign [2.0] [3rd]
[06:23:28] -OperServ- Módulo: bs_quotes [$Id: bs_quotes.c v1.1.1 20-06-2007 mikea $] [3rd]
[06:23:28] -OperServ- Módulo: cs_appendtopic [$Id: cs_appendtopic.c 1332 2008-01-04 10:43:21Z geniusdex $] [Supported]
[06:23:28] -OperServ- Módulo: cs_enforce [$Id: cs_enforce.c 1335 2008-01-06 13:38:15Z geniusdex $] [Supported]
[06:23:28] -OperServ- Módulo: cs_access_notice [$Id: cs_access_notice.c v1.0.0 29-02-2008 n00bie $] [3rd]
[06:23:28] -OperServ- Módulo: enc_none [$Id$] [Encryption]
[06:23:28] -OperServ- Módulo: global_randquotes [$Id: global_randquotes.c v1.0.1 27-08-2007 n00bie $] [3rd]
[06:23:28] -OperServ- Módulo: hs_request [$Id$] [Supported]
[06:23:28] -OperServ- Módulo: hs_nethost [2.2 [u ]] [3rd]
[06:23:28] -OperServ- Módulo: inspircd11 [$Id: inspircd11.c 2007-08-28 10:09 GMT -5 katsklaw $] [Protocol]
[06:23:28] -OperServ- Módulo: ircd_init [$Id: ircd_init.c v3.0.0 20-5-2008 n00bie $] [3rd]
[06:23:28] -OperServ- Módulo: ircd_wallonreg [2.1] [3rd]
[06:23:28] -OperServ- Módulo: ircd_community_info [1.0.1] [3rd]
[06:23:28] -OperServ- Módulo: ircd_clan_info [1.0.0] [3rd]
[06:23:28] -OperServ- Módulo: ms_limitsend [$Id: ms_limitsend.c v2.0.0, 13-11-2007 n00bie $] [3rd]
[06:23:28] -OperServ- Módulo: ns_maxemail [$Id: ns_maxemail.c 1332 2008-01-04 10:43:21Z geniusdex $] [Supported]
[06:23:28] -OperServ- Módulo: ns_masset [$Id: ns_masset.c v1.0.0 19-10-2006 n00bie $] [3rd]
[06:23:28] -OperServ- Módulo: ns_ajoin [4.2.1] [3rd]
[06:23:28] -OperServ- Módulo: ns_joinhelpchan [$Id: ns_joinhelpchan.c v2.0.0 03-02-2008 n00bie $] [3rd]
[06:23:28] -OperServ- Módulo: ns_regcode [$Id: ns_regcode.c v2.0.0 23-08-2007 n00bie $] [3rd]
[06:23:28] -OperServ- Módulo: ns_locknickreg [0.1] [3rd]
[06:23:28] -OperServ- Módulo: ns_noticeunregister [$Id: ns_noticeunregister.c v1.0.1 20-02-2008 n00bie $] [3rd]
[06:23:28] -OperServ- Módulo: os_info [$Id: os_info.c 1332 2008-01-04 10:43:21Z geniusdex $] [Supported]
[06:23:28] -OperServ- Módulo: os_access_levels [2.3] [3rd]
[06:23:28] -OperServ- Módulo: os_extrainfo [$Id: os_extrainfo.c v2.0.0 20-08-2007 n00bie $] [3rd]
Title: Re: InspIRCd + Anope problem
Post by: katsklaw on September 29, 2008, 10:35:39 AM
yes, os_access_levels version 2.3 does. I backed the version back to 2.2 because of it and it was announced here on the forum.
Title: InspIRCd + Anope problem
Post by: Andrey on September 29, 2008, 10:45:09 AM
my problem its this module  >:( -> cs_access_notice

any idea for fix this module?

Thanks a lot for all, great help.
Title: Re: [SOLVED] problem
Post by: Jan Milants on September 29, 2008, 05:18:33 PM
I would suggest you contact the module's author about this... it s a rather serious bug in the code.

Code: [Select]
if (argc < 2) {
return MOD_CONT;
}
...
if (stricmp(u->nick, argv[2]) == 0) {
return MOD_CONT;
}
the check for argc doesn't mean there is a argv[2].. it means a argv[0] and argv[1].
this particular event (EVENT_ACCESS_DEL) can be send with both 2 or 3 arguments, depending on what information is available, the module doesn't take this into account.