Anope IRC Services

Anope Support => 1.6.x (Read Only) => Topic started by: CoreDuo on August 15, 2008, 03:47:54 AM

Title: Segmentation faults
Post by: CoreDuo on August 15, 2008, 03:47:54 AM
Code: [Select]
[Aug 14 22:35:50.731185 2008] debug: Received: :TRAiNER4 PRIVMSG NickServ@services.r-type.ca :update
[Aug 14 22:35:50.733397 2008] debug: Sent: :HostServ NOTICE TRAiNER4 :Your vhost of ^Btrainer4.ath.cx^B is now activated.
[Aug 14 22:35:50.733848 2008] debug: Sent: :services.r-type.ca CHGHOST TRAiNER4 trainer4.ath.cx
[Aug 14 22:35:50.734372 2008] debug: Sent: :NickServ NOTICE TRAiNER4 :Status updated (memos, vhost, chmodes, flags).
[Aug 14 22:35:50.734874 2008] debug: Sent: :OperServ SVSJOIN TRAiNER4 :#Hypnos,#OSP
[Aug 14 22:35:50.735141 2008] debug: Sent: :NickServ NOTICE TRAiNER4 :Joining your ajoin channels #Hypnos,#OSP
[Aug 14 22:35:50.737591 2008] debug: Received: :yavin.r-type.ca NOTICE services.r-type.ca :*** /ChgHost Error: requested host is same as current host.
[Aug 14 22:35:50.737787 2008] unknown message from server (:yavin.r-type.ca NOTICE services.r-type.ca :*** /ChgHost Error: requested host is same as current$
[Aug 14 22:35:51.279417 2008] debug: Received: :CoreDuo PRIVMSG nickserv :identify <password>
[Aug 14 22:35:51.279683 2008] NickServ: Failed IDENTIFY for CoreDuo!CoreDuo@coreduo.me.uk
[Aug 14 22:35:51.280318 2008] debug: Sent: :NickServ NOTICE CoreDuo :Password incorrect.
[Aug 14 22:35:51.280935 2008] PANIC! buffer = :CoreDuo PRIVMSG nickserv :identify <password>
[Aug 14 22:35:51.293027 2008] debug: Sent: :services.r-type.ca GLOBOPS :PANIC! buffer = :CoreDuo PRIVMSG nickserv :identify <password>
[Aug 14 22:35:51.293432 2008] Services terminating: Segmentation fault
[Aug 14 22:35:51.303708 2008] debug: Sent: :services.r-type.ca SQUIT services.r-type.ca :Services terminating: Segmentation fault

What happens is, anope is started, works fine, but when someone identifies, it segfaults. I have tried recompiling anope, to no avail. It happens whether or not the password is correct.

EDIT: It appears as though Anope 1.6 does not work correctly with GCC 4. I installed GCC 3.4 and everything worked fine.
Title: Re: Segmentation faults
Post by: Jan Milants on August 15, 2008, 11:45:12 AM
anope 1.6 is near to end-of-life ... i don't think it will be updated to work with newest compilers... heck it doesn't even fully support most current ircd's..  :-\
Title: Re: Segmentation faults
Post by: CoreDuo on August 15, 2008, 05:39:55 PM
A new stable version would be nice then ;)

I don't feel entirely comfortable with running the development version on a main network.

Thanks anyway
Title: Re: Segmentation faults
Post by: Jobe on August 15, 2008, 07:31:58 PM
Changes such as supporting newer compilers are really too big of a change for the stable branch anyway.

There will hopefully be a whole new stable branch soon anyway based off of the 1.7.* branch, which is considered as stable as the 1.6.* branch now anyway even though it's the development branch.
Title: Re: Segmentation faults
Post by: CoreDuo on August 15, 2008, 09:52:34 PM
Just a suggestion, but you could have the compile cancel if gcc >3.4. Temporary fix until new stable branch is out :)
Title: Re: Segmentation faults
Post by: Jan Milants on August 15, 2008, 10:04:49 PM
that would still require a new version of 1.6 to be released... as far as i know that would only be done if security issues arise.. most people already use the 1.7 branch anyaways. even 1.7's next release is overdue, so i think it would be a waste of time. it s better spend on getting the next devel or 1.8 beta out..
Title: Re: Segmentation faults
Post by: Jobe on August 15, 2008, 10:07:05 PM
I'm in agreement with Viper. 1.6.* is getting so close to the end of it's life that effort is probably wasted on maintaining it.
Title: Re: Segmentation faults
Post by: katsklaw on August 15, 2008, 11:30:12 PM
A new stable version would be nice then ;)

I don't feel entirely comfortable with running the development version on a main network.

Thanks anyway

1.7.21 is just a release or 2 away from being 1.8 Stable so it's as stable as it's going to get. Go ahead and upgrade.

READ ALL DOCS BEFORE UPGRADING!!