Re: [sr-dev] 3.3 presence crash

now i got pua.c crash without any close by publish request: Program terminated with signal 11, Segmentation fault. #0 0x00007f4bc97766a6 in db_update (ticks=28098484, param=0x0) at pua.c:992 992 switch(p->db_flag) (gdb) where #0 0x00007f4bc97766a6 in db_update (ticks=28098484, param=0x0) at pua.c:992 #1 0x0000000000507b6a in compat_old_handler (ti=449575751, tl=0x7f4bc6212050, data=0x7f4bc6212050) at timer.c:1017 #2 0x00000000005080ac in slow_timer_main () at timer.c:1151 #3 0x000000000045c7f8 in main_loop () at main.c:1688 #4 0x000000000045f29c in main (argc=16, argv=0x7fff1c7fa078) at main.c:2546 there was pua publish at 09:18:45 but there was no subscribers for the presentity at that time. then at 09:19:42, there was subscription for this presentity and crash followed right after notify was generated. i have not set any presence related db_mode parameters. i don't remember seeing these crashes in may when i did similar presence tests. -- juha _______________________________________________ sr-dev mailing list sr-dev(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev