[Devel] [ openser-Bugs-1553878 ] siptrace setflag crash

SourceForge.net noreply at sourceforge.net
Thu Nov 23 10:17:25 CET 2006


Bugs item #1553878, was opened at 2006-09-07 08:08
Message generated for change (Comment added) made by hwaastad
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1553878&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: ver 1.1.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Helge Waastad (hwaastad)
Assigned to: Bogdan (bogdan_iancu)
Summary: siptrace setflag crash

Initial Comment:
By setting siptrace flag for a register request,
openser suddenly crashes.

Back trace from transaction:

>>>>>(gdb) bt
>>>>>#0  0x000000304448660b in strftime_l () from
/lib64/tls/libc.so.6
>>>>>#1  0x0000002a95b29de4 in time2mysql
(_time=Variable "_time" is not
>>>>>available.
>>>>>) at utils.c:54
>>>>>#2  0x0000002a95b2a731 in val2str (_c=Variable
"_c" is not available.
>>>>>) at val.c:147
>>>>>#3  0x0000002a95b26b13 in print_values (_c=0x643648,
>>>>>  _b=0x2a95db5269 "'SIP/2.0 100 Trying\\r\\nVia:
SIP/2.0/UDP
>>>>>217.17.222.4;branch=z9hG4bK1957.c42a1af6.0\\r\\nVia:
SIP/2.0/UDP
>>>>>10.1.93.186:10001;rport=44323;received=217.17.222.6;branch=z9hG4bK2eb74daf34599095\\r\\nFrom:
\\\"Har"..., _l=65431, _v=0x7fbfffe990, _n=10) at
dbase.c:144
>>>>>#4  0x0000002a95b27aa4 in db_insert (_h=0x643e08,
_k=Variable "_k" is
>>>>>not available.
>>>>>) at dbase.c:495
>>>>>#5  0x0000002a97c26bdc in trace_sl_onreply_out
(req=Variable "req" is
>>>>>not available.
>>>>>) at siptrace.c:1078
>>>>>#6  0x0000002a956b30ad in run_sl_callbacks
(req=0x643f28,
>>>>>buffer=Variable "buffer" is not available.
>>>>>) at sl_cb.c:88
>>>>>#7  0x0000002a956b3608 in sl_send_reply
(msg=0x643f28, code=100,
>>>>>text=0x608ee8 "Trying") at sl_funcs.c:149
>>>>>#8  0x0000000000409c38 in do_action
(a=dwarf2_read_address: Corrupted
>>>>>DWARF expression.
>>>>>) at action.c:701
>>>>>#9  0x000000000040a87e in do_action
(a=dwarf2_read_address: Corrupted
>>>>>DWARF expression.
>>>>>) at action.c:89
>>>>>#10 0x000000000040b43d in do_action
(a=dwarf2_read_address: Corrupted
>>>>>DWARF expression.
>>>>>) at action.c:89
>>>>>#11 0x000000000040b496 in do_action
(a=dwarf2_read_address: Corrupted
>>>>>DWARF expression.
>>>>>) at action.c:89
>>>>>#12 0x000000000040b762 in run_top_route
(a=Variable "a" is not
>>>>>available.
>>>>>) at action.c:89
>>>>>#13 0x000000000043188c in receive_msg
(buf=0x2a97e4d2f8 "\026", len=822,
>>>>>rcv_info=0x7fbffff810) at receive.c:155
>>>>>#14 0x000000000044fc74 in udp_rcv_loop () at
udp_server.c:465
>>>>>#15 0x000000000041f7f4 in main_loop () at main.c:925
>>>>>#16 0x0000000000420446 in main (argc=Variable
"argc" is not available.
>>>>>) at main.c:1477

----------------------------------------------------------------------

>Comment By: Helge Waastad (hwaastad)
Date: 2006-11-23 10:17

Message:
Logged In: YES 
user_id=1536165
Originator: YES

Hi,
I have not seen a crash after the upgrade.
And I've been running for a couple of months now

hw


----------------------------------------------------------------------

Comment By: Bogdan (bogdan_iancu)
Date: 2006-11-22 17:15

Message:
Logged In: YES 
user_id=1275325
Originator: NO

Helge,

any feedback on this? was the crash related to the mysq installation (and
fixed after your machine upgrade) or you still experince it?

regards,
bogdan

----------------------------------------------------------------------

Comment By: Helge Waastad (hwaastad)
Date: 2006-09-21 13:50

Message:
Logged In: YES 
user_id=1536165

I have started to check if I can reproduce the problem.
However, there has been some upgrades don in my system,
(mysql 5.0.24) and the CentOS system.

I will monitor my cluster and give feedback.

br hw

----------------------------------------------------------------------

Comment By: Bogdan (bogdan_iancu)
Date: 2006-09-20 14:41

Message:
Logged In: YES 
user_id=1275325

I was not able to reproduce the bug - tried enabling
siptrace for a REGISTER and sending 100 Trying reply before
save().
Anyhow, the trace shows the crash in mysql module when
printing a time stamp. quite strange.....
are you able to reproduce the bug on other systems? can you
provide a tarball with source + binaries + corefile?

Also, please attached the configuration of the siptrace
module (the module params).

thanks,
bogdan

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1553878&group_id=139143



More information about the Devel mailing list