here is a trace from the coredump:
```
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f12607da547 in atomic_cmpxchg_int (var=0x8, old=0, new_v=1) at ../../core/mem/../atomic/atomic_x86.h:224
224 ATOMIC_FUNC_CMPXCHG(cmpxchg, "cmpxchgl %2, %1", int , int)
(gdb) up
#1 0x00007f12607da57b in futex_get (lock=0x8) at ../../core/mem/../futexlock.h:99
99 v=atomic_cmpxchg(lock, 0, 1); /* lock if 0 */
(gdb)
#2 0x00007f12607fe0d0 in update_db_subs_timer_dbnone (no_lock=0) at subscribe.c:2079
2079 lock_get(&subs_htable[i].lock);
(gdb) up
#3 0x00007f1260802121 in timer_db_update (ticks=61825161, param=0x0) at subscribe.c:2441
2441 update_db_subs_timer_dbnone(no_lock);
(gdb) up
#4 0x00005568ade05b2e in sr_wtimer_exec (ticks=61825161, param=0x0) at core/timer_proc.c:433
433 wt->f(ticks, wt->param);
(gdb) up
#5 0x00005568ade04b58 in fork_sync_timer (child_id=-1, desc=0x5568ae01a3a1 "secondary timer", make_sock=1, f=0x5568ade057a8 <sr_wtimer_exec>, param=0x0, interval=1000) at core/timer_proc.c:267
267 f(TICKS_TO_S(ts1), param); /* ticks in sec for compatibility with old
(gdb) up
#6 0x00005568ade05ece in sr_wtimer_start () at core/timer_proc.c:459
459 if(fork_sync_timer(-1 /*PROC_TIMER*/, "secondary timer", 1,
(gdb) up
#7 0x00005568adc05e24 in main_loop () at main.c:1452
1452 if(sr_wtimer_start()<0) {
(gdb) up
#8 0x00005568adc123e7 in main (argc=9, argv=0x7ffd9501a8a8) at main.c:2845
2845 ret=main_loop();
(gdb) up
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/f917318c1e5fefa4106eaaf46123506…
getting coredump and seeing this in log:
```
3(5514) DEBUG: presence [subscribe.c:711]: msg_watchers_clean(): cleaning pending subscriptions
0(5505) ALERT: <core> [main.c:775]: handle_sigs(): child process 5514 exited by a signal 11
0(5505) ALERT: <core> [main.c:778]: handle_sigs(): core was generated
0(5505) INFO: <core> [main.c:798]: handle_sigs(): dont_fork turned on, living on
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/f917318c1e5fefa4106eaaf46123506…
> @eschmidbauer - can you help testing somehow? Not having the possibility to test properly here, working mainly from home these days I can't use many devices. First would be to make sure existing your existing config is still working fine. I tried to be very non-intrusive as much as possible in the old code and operation mode.
>
> Then, to test in-memory only presentity records, set:
>
> ```
> modparam("presence", "publ_cache", 2)
> ```
>
> You have to use latest master branch. I did basic tests with baresip for handling the PUBLISH requests and I could see they are in database presentity table if publ_cache!=2 as well as in memory via rpc command if publ_cache==2.
>
> You can set also subscription records in memory with:
>
> ```
> modparam("presence", "subs_db_mode", 0)
> ```
yes- i'll see what i can do and report back to you. im assuming i'll have to compile master branch for these features.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/f917318c1e5fefa4106eaaf46123506…