[Users] Daemons and killing processes...

[Bogdan-Andrei Iancu]

Hi,

you mean that after first register the proxy dies? if so, it seams like 
a mem corruption to me...any logs? the memory debugger messages are very 
useful.

regards,
bogdan

Helge Waastad wrote:

> Hi,
> this is the output after compiling with the extra options.
>
> Anyway, that really killed the daemon..
> One register, and it dumps.
>
> br hw
>
>
> (gdb) bt
> #0  0x002727a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> #1  0x00338d8c in sched_yield () from /lib/tls/libc.so.6
> #2  0x00e4b100 in lock_udomain (_d=0xb618fe58) at ../../fastlock.h:166
> #3  0x00e4db9a in mem_timer_udomain (_d=0xb618fe58) at udomain.c:677
> #4  0x00e47f05 in synchronize_all_udomains () at dlist.c:488
> #5  0x00e50a15 in destroy () at ul_mod.c:285
> #6  0x08085dce in destroy_modules ()
> #7  0x080638ba in cleanup ()
> #8  0x080644f6 in handle_sigs ()
> #9  0x08065215 in main_loop ()
> #10 0x08065835 in main ()
>
>
> Mvh,
> Helge Waastad
> Senior Engineer
> Smartnet
> tlf: 67830017
>
>
>
> -----Original Message-----
> From: Bogdan-Andrei Iancu [mailto:bogdan at voice-system.ro]
> Sent: Tue 3/7/2006 9:17 PM
> To: Helge Waastad
> Cc: Andreas Granig; users at openser.org
> Subject: Re: [Users] Daemons and killing processes...
>
> Hi Helge,
>
> I suspect a problem related to memory - the remaining process may cycle
> with no control trying to print the mem status (which may be broken).
>
> to see if it;s the case, compile mem debug support (remove F_MALLOC and
> add DBG_QM_MALLOC and recompile everything)
>
> regards,
> bogdan
>
> Helge Waastad wrote:
>
> >Hi,
> >I've been waiting fo 12 min now, and are preparing to put then kettle on
> >to fix me a cup of coffee...I guess I have time enough :-)
> >
> >...is there a "debugging" manual avaliable? I guess it would be nice
> >having feedback on the dev list already including the backtrace?
> >
> >
> >BTW, the output for the hanging process is:
> >
> >(gdb) bt
> >#0  0x080a0ab9 in fm_status ()
> >#1  0x080663e2 in sig_usr ()
> >#2  <signal handler called>
> >#3  0x007787a0 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> >#4  0x008594d1 in recvfrom () from /lib/tls/libc.so.6
> >#5  0x08098a87 in udp_rcv_loop ()
> >#6  0x08066df2 in main_loop ()
> >#7  0x08067585 in main ()
> >
> >
> >
> >
> >tir, 07,.03.2006 kl. 18.56 +0100, skrev Andreas Granig:
> > 
> >
> >>Helge Waastad wrote:
> >>   
> >>
> >>>Hi,
> >>>I have somewhat trouble to get a core dump from the init script.
> >>>I get core dumps when I run it in shell, but not as init script.
> >>>
> >>>I'll try to be creative later this evening.
> >>>     
> >>>
> >>The backtrace for the processes looks like this:
> >>
> >>#0  0x0808eb0d in fm_status (qm=0x811d940) at mem/f_malloc.c:515
> >>#1  0x08065fee in sig_usr (signo=1077141592) at main.c:565
> >>#2  <signal handler called>
> >>#3  0x4010d534 in recvfrom () from /lib/libc.so.6
> >>#4  0x08089433 in udp_rcv_loop () at udp_server.c:415
> >>#5  0x08063de4 in main_loop () at main.c:919
> >>#6  0x0806522e in main (argc=1, argv=0xbfbc54e4) at main.c:1472
> >>
> >>But it shuts down after quite some (long) time...
> >>
> >>Andy
> >>   
> >>
>
>