Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: 1.9.7 next problem - crash on nick expire ?!  (Read 4354 times)

0 Members and 1 Guest are viewing this topic.

Michael

  • Anope User
  • Offline Offline
  • Posts: 10
1.9.7 next problem - crash on nick expire ?!
« on: April 26, 2012, 01:20:20 PM »



[Apr 26 11:30:06.915451 2012] Debug: Expiring nickname Julian (group: Julian) (e-mail: julian@*********.de)
[Apr 26 11:30:06.915874 2012] Debug: deleting nickname group Julian


Program received signal SIGSEGV, Segmentation fault.
0x00000000004d1b18 in std::_Rb_tree<dynamic_reference_base*, dynamic_reference_base*, std::_Identity<dynamic_reference_base*>, std::less<dynamic_reference_base*>, std::allocator<dynamic_reference_base*> >::_M_begin (this=0x1764e50) at /usr/include/c++/4.4/bits/stl_tree.h:482
482           { return static_cast<_Link_type>(this->_M_impl._M_header._M_parent); }

Logged

Eyecu

  • Anope User
  • Offline Offline
  • Posts: 29
Re: 1.9.7 next problem - crash on nick expire ?!
« Reply #1 on: April 27, 2012, 10:44:30 PM »

I take it your using it with mysql, if so try disabling it until they fix it.  I had to disable mysql and since i did services have been running pretty stable.
Logged

Michael

  • Anope User
  • Offline Offline
  • Posts: 10
Re: 1.9.7 next problem - crash on nick expire ?!
« Reply #2 on: April 27, 2012, 10:49:54 PM »

We use "db_flatfile" database for nicks and channel
But have actively Chanstats with mysql

I will disable the Chanstats, and test it

Thanks for the note
Logged

Michael

  • Anope User
  • Offline Offline
  • Posts: 10
Re: 1.9.7 next problem - crash on nick expire ?!
« Reply #3 on: April 27, 2012, 11:26:32 PM »

No, it was not there - same error

Code: [Select]
[Apr 27 22:21:24.676379 2012] Debug: Received: :1S1 PING 1S1 1G2
[Apr 27 22:21:24.676524 2012] Debug: Sent: :1G2 PONG 1G2 1S1
[Apr 27 22:22:19.676033 2012] Debug: Expiring nickname Julian (group: Julian) (e-mail: julian@hidden.tld)
[Apr 27 22:22:19.676448 2012] Debug: deleting nickname group Julian

Program received signal SIGSEGV, Segmentation fault.
0x00000000004d1b18 in std::_Rb_tree<dynamic_reference_base*, dynamic_reference_base*, std::_Identity<dynamic_reference_base*>, std::less<dynamic_reference_base*>, std::allocator<dynamic_reference_base*> >::_M_begin (this=0x1826f90) at /usr/include/c++/4.4/bits/stl_tree.h:482
482           { return static_cast<_Link_type>(this->_M_impl._M_header._M_parent); }
(gdb)
Logged

Michael

  • Anope User
  • Offline Offline
  • Posts: 10
Re: 1.9.7 next problem - crash on nick expire ?!
« Reply #4 on: April 28, 2012, 02:05:31 PM »

The attempt to delete the nick manually went wrong, crash   :o :'(

Quote
[Apr 28 12:36:24.524993 2012] OVERRIDE: sidekix!snoopy@hidden.tld used drop to drop nickname Julian (group: Julian) (email: julian@hidden.tld)
[Apr 28 12:36:24.525073 2012] Debug: Sent: :1G2AAAAAF PRIVMSG #hidden.secret :OVERRIDE: sidekix!snoopy@hidden.tld used drop to drop nickname Julian (group: Julian) (email: julian@hidden.tld)
[Apr 28 12:36:24.525365 2012] Debug: deleting nickname group Julian
[Apr 28 12:36:24.525415 2012] Debug: Sent: :1G2AAAAAF PRIVMSG #hidden.secret :deleting nickname group Julian

Program received signal SIGSEGV, Segmentation fault.
0x00000000004d1b18 in std::_Rb_tree<dynamic_reference_base*, dynamic_reference_base*, std::_Identity<dynamic_reference_base*>, std::less<dynamic_reference_base*>, std::allocator<dynamic_reference_base*> >::_M_begin (this=0x18556b0) at /usr/include/c++/4.4/bits/stl_tree.h:482
482           { return static_cast<_Link_type>(this->_M_impl._M_header._M_parent); }

confused...

Attachment: new full bt
Logged
Pages: [1]   Go Up