Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: [2.0.2] ChanServ TOPIC Crashes Anope  (Read 7333 times)

0 Members and 1 Guest are viewing this topic.

TwinShadow

  • Anope User
  • Offline Offline
  • Posts: 64
    • ShadowHime
[2.0.2] ChanServ TOPIC Crashes Anope
« on: July 13, 2015, 11:09:46 AM »

Finally got around to upgrading the services on my network to 2.0.2, and ran into a few snags, but managed to debug them fine, until I tried using the TOPIC command.

Generally, it works, only half way. In short, if I were to issue this command: /cs topic #channel Some random text - no matter what, seems to cause the services to crash. Now, I know what you all may want, something in the log. Well.. no dice. Why? Because it doesn't output a log for the crash. I already ran the services in --debug mode and it still didn't log anything of note.

Right now, I'm using InspIRCd 2.0.20, but I'm not sure if its a module conflict, or something in my config that's causing the crash. This is the last line before the services crash: [Jul 13 10:05:30 2015] Received: :35UAAAABO PRIVMSG 36TAAAAAC :topic #services Some random text - Hard to believe, but nothing in the log really tells me anything.

Hopefully someone can help me out. Its a bit of a perplexing issue, but I'm wondering if it some sort of issue in my config maybe, in either IRCd or the services themselves.
Logged

Charles Kingsley

  • Contributor
  • *
  • Offline Offline
  • Posts: 1405
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #1 on: July 13, 2015, 11:12:26 AM »

Run it through gdb in debug mode so you get something :)
Logged

TwinShadow

  • Anope User
  • Offline Offline
  • Posts: 64
    • ShadowHime
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #2 on: July 13, 2015, 11:32:25 AM »

Been a long time since I used GDB, maybe... well over a year? Just so I do it correctly before I run it through there, its a simple type of gdb, and then run Anope like normal with the debug?
Logged

Charles Kingsley

  • Contributor
  • *
  • Offline Offline
  • Posts: 1405
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #3 on: July 13, 2015, 11:33:48 AM »

Yeah, run it with -debug -nofork and once it blows up type bt full
Logged

TwinShadow

  • Anope User
  • Offline Offline
  • Posts: 64
    • ShadowHime
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #4 on: July 13, 2015, 12:01:31 PM »

Well, as it turns out, I do not have access to gdb on the server. More like, it don't exist. I let the person in charge know about it, but in the meantime I did notice that while in the -nofork, it Seg Faulted. But, I will report back if I can get gdb access to provide a better output.
Logged

Charles Kingsley

  • Contributor
  • *
  • Offline Offline
  • Posts: 1405
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #5 on: July 13, 2015, 12:02:55 PM »

cool, thanks.
Logged

Adam

  • Team
  • *
  • Offline Offline
  • Posts: 463
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #6 on: July 13, 2015, 12:41:31 PM »

Get gcc --version
Logged

TwinShadow

  • Anope User
  • Offline Offline
  • Posts: 64
    • ShadowHime
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #7 on: July 13, 2015, 12:44:06 PM »

gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-55)

Don't look at me for the old version. Something that can't be helped.
Logged

Adam

  • Team
  • *
  • Offline Offline
  • Posts: 463
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #8 on: July 13, 2015, 12:46:40 PM »

We don't support gcc 4.1. You can yum install gcc44 and CXX=g++44 ./Config -quick && make -C build install to fix it by using gcc 4.4.
Logged

TwinShadow

  • Anope User
  • Offline Offline
  • Posts: 64
    • ShadowHime
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #9 on: July 13, 2015, 12:48:23 PM »

Ah I see. If that was the requirement, then I'm kinda surprised it still let me compile the current source then. Oh well.
Logged

Adam

  • Team
  • *
  • Offline Offline
  • Posts: 463
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #10 on: July 13, 2015, 12:54:32 PM »

We didn't really know we didn't support it until post 2.0. Noone develops on archaic systems.
Logged

TwinShadow

  • Anope User
  • Offline Offline
  • Posts: 64
    • ShadowHime
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #11 on: July 13, 2015, 04:10:21 PM »

Tried changing the CXX to g++44, and although ECHO $CXX returns g++44, the compiler still only reads from the old binary which is 4.1. So I'm kinda stumped on this currently.
Logged

Adam

  • Team
  • *
  • Offline Offline
  • Posts: 463
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #12 on: July 13, 2015, 04:17:20 PM »

Try removing the build directory before reconfiguring, rm -rf build
Logged

TwinShadow

  • Anope User
  • Offline Offline
  • Posts: 64
    • ShadowHime
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #13 on: July 13, 2015, 04:37:46 PM »

Should of mentioned that, but that had already been done. I actually removed the entire source directory, extracted a brand new one. It still pulled from the old binary. The best I can think of right now is either A:) get the server admin to update the server, or B:) install from source updated compilers and modifying PATH.
Logged

Adam

  • Team
  • *
  • Offline Offline
  • Posts: 463
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #14 on: July 13, 2015, 04:39:05 PM »

Did you actually install gcc 4.4? g++44 --version should return something.
Logged

TwinShadow

  • Anope User
  • Offline Offline
  • Posts: 64
    • ShadowHime
Re: [2.0.2] ChanServ TOPIC Crashes Anope
« Reply #15 on: July 13, 2015, 04:53:31 PM »

I don't have root on the server. But g++44 did return 4.4.7. Problem is, for some reason the compiler just did not want to use it, even when I set CXX=g++44. Why, I have no clue.

[edit] Some good news out of this, which is mostly good anyway for Anope. He got a dev tool installed and it uses a much more current version of G++ (like 4.7 I think), and modified a PATH line for it. Compiled with that after clearing the build folder, and now that command no longer crashes.

Now to fix stuff for ZNC..
« Last Edit: July 13, 2015, 05:21:48 PM by TwinShadow »
Logged
Pages: [1]   Go Up