[IRCServices Coding] Services 5

Andrew Church achurch at achurch.org
Mon Dec 17 07:57:24 PST 2001


>On Monday 17 December 2001 09:33, Andrew Church wrote:
>> >Here's a backtrace from that particuliar problem.
>> >
>> >(gdb) bt
>> >#0  0x4015ccbc in ?? ()
>> >#1  0x080535fb in unload_module (module=0x812a0c8) at modules.c:406
>> >#2  0x08053135 in modules_exit () at modules.c:109
>> >#3  0x08051b90 in main (ac=1, av=0xbffffadc, envp=0xbffffae4) at
> main.c:406
>> >#4  0x4003ce5e in __libc_start_main (main=0x805177c <main>, argc=1
>,
>> >    ubp_av=0xbffffadc, init=0x804b9a4 <_init>, fini=0x8057bc0 <_
>fini>,
>> >    rtld_fini=0x4000d3c4 <_dl_fini>, stack_end=0xbffffacc)
>> >    at ../sysdeps/generic/libc-start.c:129
>> 
>>      Looks like some module is forgetting to remove its callbacks.  Can
> you
>> play around with commenting/uncommenting your LoadModule directives in
>> services.conf until you find the module that causes the problem?
>
>Trying an:
>
>(gdb) up
>(gdb) p module->name
>
>whould show the module name

     No, that would show the name of the module being unloaded, not the one
whose callback was being called.

  --Andrew Church
    achurch at achurch.org
    http://achurch.org/