Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Segmentation fault detected  (Read 3008 times)

0 Members and 1 Guest are viewing this topic.

DragonRyder

  • Anope User
  • Offline Offline
  • Posts: 64
    • http://www.XeroMem.com
Segmentation fault detected
« on: November 29, 2006, 02:39:24 AM »

services said to report this - so here it is:
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace: Segmentation fault detected
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace: report the following lines
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace: Anope version 1.7.17 (1182) build #1, compiled Oct 26 2006 17:30:14  EM
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace(0): ./services(do_backtrace+0x51) [0x80703b1]
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace(1): ./services(sighandler+0x10d) [0x8070ead]
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace(2): [0xffffe420]
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace(3): ./services(destroyModule+0x2b) [0x807802b]
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace(4): ./services(delModule+0x79) [0x8078109]
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace(5): ./services(modules_unload_all+0xa2) [0x8078952]
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace(6): ./services(sighandler+0x17e) [0x8070f1e]
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace(7): [0xffffe420]
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace(8): ./services(destroyModule+0x2b) [0x807802b]
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace(9): ./services(delModule+0x79) [0x8078109]
[Tue. Nov. 28 2006 9:34pm] <@Global> Backtrace: complete
[Tue. Nov. 28 2006 9:34pm] <@Global> Services terminating: Segmentation fault

sorry if this is in the wrong spot
Logged
From the depths of Hell I hear you cry.

heinz

  • Guest
(No subject)
« Reply #1 on: November 29, 2006, 02:49:38 AM »

Looks like a module issue.. paste the output of: /msg operserv modlist

Probably also help if you got a gdb backtrace. See: http://anope.info/Other:GDB

[Edited on 29-11-2006 by heinz]
Logged

DragonRyder

  • Anope User
  • Offline Offline
  • Posts: 64
    • http://www.XeroMem.com
(No subject)
« Reply #2 on: November 29, 2006, 02:59:59 AM »

[Tue. Nov. 28 2006 9:54pm] -OperServ- Current Module list:
[Tue. Nov. 28 2006 9:54pm] -OperServ- Module: cs_appendtopic [$Id: cs_appendtopic.c 1122 2006-08-06 15:00:13Z certus $] [Supported]
[Tue. Nov. 28 2006 9:54pm] -OperServ- Module: cs_enforce [$Id: cs_enforce.c 957 2006-01-24 07:54:48Z certus $] [Supported]
[Tue. Nov. 28 2006 9:54pm] -OperServ- Module: ircd_vhostserv [$Id: ircd_vhostserv.c v1.0.1 04-10-2006 n00bie $] [3rd]
[Tue. Nov. 28 2006 9:54pm] -OperServ- Module: ns_maxemail [$Id: ns_maxemail.c 953 2006-01-14 11:36:29Z certus $] [Supported]
[Tue. Nov. 28 2006 9:54pm] -OperServ- Module: os_info [$Id: os_info.c 1162 2006-09-29 17:54:07Z geniusdex $] [Supported]
[Tue. Nov. 28 2006 9:54pm] -OperServ- Module: os_forceid [$Id: os_forceid.c v1.0.0 05-10-2006 n00bie $] [3rd]
[Tue. Nov. 28 2006 9:54pm] -OperServ- Module: os_clientjoin [1.02] [3rd]
[Tue. Nov. 28 2006 9:54pm] -OperServ- Module: os_notinchanlist [2.1b +S] [3rd]
[Tue. Nov. 28 2006 9:54pm] -OperServ- Module: unreal32 [$Id: unreal32.c 1159 2006-09-28 08:52:35Z certus $] [Protocol]
[Tue. Nov. 28 2006 9:54pm] -OperServ- 9 Modules loaded.

i removed these:
profileserv.c
bs_assign_limit.c
bs_seen.c
cs_autoowner.c
unban_services.c
cs_default_topic.c
Logged
From the depths of Hell I hear you cry.

heinz

  • Guest
(No subject)
« Reply #3 on: November 29, 2006, 03:01:05 AM »

You will need to get a GDB backtrace if you want us to pin down the segfault..
Logged

DragonRyder

  • Anope User
  • Offline Offline
  • Posts: 64
    • http://www.XeroMem.com
(No subject)
« Reply #4 on: November 29, 2006, 03:42:01 AM »

i pasted it here cause it told me to.

if it happens again - then i will go the gdb thingy you asked about.
Logged
From the depths of Hell I hear you cry.

heinz

  • Guest
(No subject)
« Reply #5 on: November 29, 2006, 03:46:19 AM »

Well, it's really only saying "if you want the bug/issue to be found you will need these lines to start off with"... :)

Like I say though, it looks likely to be a 3rd party module thats causing this.. but yeah, a gdb trace of the problem if it happens again would be nice.
Logged

Jan Milants

  • Team
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 1372
(No subject)
« Reply #6 on: November 29, 2006, 04:39:45 PM »

what was the last line before the segfault ?

sometimes also gives a hint as to what caused it...
Logged
If you like me donate coins to 1FBmZVT4J8WAUMHKqpWhgNVj3XXnRN1cCk :)
Pages: [1]   Go Up