Hi,

After many many months of faultless operation, today we experienced a SEG FAULT on one of our proxies running OpenSER 1.1.0-notls:

Below is a back trace (with some values masked with xxx's), however our initial analysis can not make any sense of what the problem is. Any ideas would be greatly appreciated.

res.c:194 is =====> r = (db_res_t*)pkg_malloc(sizeof(db_res_t));

Here is the back trace:

(gdb) bt
#0 0x00000000 in ?? ()
#1 0x4016ad2c in new_result () at res.c:194
#2 0x4016a495 in store_result (_h=0x81301b8, _r=0xbffff198) at dbase.c:322
#3 0x404bfc0a in db_load_avp (uuid=0x81301b8, username=0x81301b8, domain=0x81301b8, attr=0x81301b8 "@X\022\bų\034\023\b",
    table=0x0, scheme=0x404ce9e0) at avpops_db.c:270
#4 0x404c05d6 in ops_dbload_avps (msg=0x8134cd8, sp=0x8128210, dbp=0x8128b18, use_domain=0) at avpops_impl.c:393
#5 0x404bef47 in w_dbload_avps (msg=0x81301b8, source=0x81301b8 "@X\022\bų\034\023\b",
    param=0x81301b8 "@X\022\bų\034\023\b") at avpops.c:1183
#6 0x0805071b in do_action (a=0x8128de8, msg=0x8134cd8) at action.c:701
#7 0x08050631 in do_action (a=0x8129478, msg=0x8134cd8) at action.c:89
#8 0x08050631 in do_action (a=0x81294a8, msg=0x8134cd8) at action.c:89
#9 0x080522c2 in run_actions (a=0x8126548, msg=0x8134cd8) at action.c:89
#10 0x08051f2e in run_top_route (a=0x81301b8, msg=0x81301b8) at action.c:151
#11 0x08071ec1 in receive_msg (
    buf=0x80ea340 "REGISTER sip:xx.xxxxxxx.xxx SIP/2.0\r\nVia: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK-f1cef63e\r\nFrom: xxxxx <sip:xxxxxx@xx.xxxxxxx.xxx>;tag=fe10f354c23eb963o0\r\nTo: xxxxx < sip:xxxxxx@xx.xxxxxxx.xxx>\r\nC"..., len=475,
    rcv_info=0xbffff9a0) at receive.c:155
#12 0x08089654 in udp_rcv_loop () at udp_server.c:465
#13 0x08063b64 in main_loop () at main.c:925
#14 0x08064fae in main (argc=9, argv=0xbffffb24) at main.c:1477
(gdb) quit

Thanks in advance

Martin