[reSIProcate] Segmentation Fault after program exit

["Niraj Roy" <nroy@xxxxxxxxxx>]

Hi,

    I am preparing an application using resiprocate-0.9.0-5019.

    I have very strange problem.

    If I return from my main() function because of some parameter reading failure, 

    after doing safe exit it says segmentation fault.

    Following is the trace using gdb.

 

#0  0xb7086f7f in _int_free () from /lib/tls/libc.so.6
#1  0xb7085f78 in free () from /lib/tls/libc.so.6
#2  0xb7533192 in ares_destroy (channel=0xb714a660) at ares_destroy.c:31
#3  0xb7406ca2 in ~AresDns (this=0x852a768) at AresDns.cxx:39
#4  0xb742421a in ~DnsInterface (this=0x83b3f80) at stl_tree.h:851
#5  0xb74eb887 in ~TransportSelector (this=0x83b3f7c) at stl_tree.h:567
#6  0xb74d4af7 in ~TransactionController (this=0x83b3ef4) at TransactionController.cxx:39
#7  0xb74b89d9 in ~SipStack (this=0x8390380) at stl_tree.h:567
#8  0x08095147 in __tcf_4 ()
#9  0xb70403d3 in exit () from /lib/tls/libc.so.6
#10 0xb702b7aa in __libc_start_main () from /lib/tls/libc.so.6
#11 0x08050a59 in _start ()

One important point , here I have not initialized any of the resiprocate/dum component.

 

Can anybody shade some light on it ?

 

 

Regards, 

Niraj S. Roy
Senior Software Engineer

 

9426554400(M)
+91-79-26463403(O)
niraj@xxxxxxxxxx

______________________________________________________

The information contained in this message and any attachment may be proprietary, confidential, and privileged or subject to the work product doctrine and thus protected from disclosure.  If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it and all copies and backups thereof.  Thank you.