Daniel-Constantin Mierla writes:
Grab the gdb output for:
list
p *rule
p *pl
Here:
(gdb) list
2325 in lcr_mod.c
(gdb) p *rule
Cannot access memory at address 0x3837333334313030
(gdb) p *pl
$1 = {rule_id = 0, prefix = '\000' <repeats 15 times>, prefix_len = 5,
from_uri = '\000' <repeats 256 times>, from_uri_len = 0, mt_tvalue =
'\000' <repeats 128 times>, mt_tvalue_len = 0, from_uri_re = 0x0,
request_uri = '\000' <repeats 256 times>, request_uri_len = 0,
request_uri_re = 0x0, stopper = 0, enabled = 0, targets = 0x0, next =
0x0}
We noticed that there has been two back-to-back lcr.reload calls:
Nov 17 08:06:24 rox1 /usr/bin/sip-proxy[1503]: INFO: Executing JSON
request
<{"jsonrpc":"2.0","method":"lcr.reload","params":[],"id":1}>
from <x.x.x.x> with host <y.y.y.y:6060>
Nov 17 08:06:25 rox1 /usr/bin/sip-proxy[1503]: INFO: Executing JSON
request
<{"jsonrpc":"2.0","method":"lcr.reload","params":[],"id":1}>
from <x.x.x.x> with host <y.y.y.y:6060>
There could be problem, if first is not finished when the second starts.
-- Juha