Hello,
the core file is useless without binaries, so you have to send the gdb
backtrace:
gdb /path/to/kamailio /path/to/corefile
Then do 'bt full' and send the output on the mailing list.
Cheers,
Daniel
On 4/27/12 8:30 PM, Gnaneshwar Gatla wrote:
Hey Daniel,
Yes, this can be reproduced. I have uploaded the xml and Kamailio log
and core files to the following ftp site.
Username: Kamailio
Password: 99Teaz
URL:
ftp://ftp.intouchhealth.com
Steps for reproducing the crash:
Use the xml(rls.xml) to be inserted in the xcap table using a
xcap_server with the help of a http client.
The service uri is sip:rls@<domainName <sip:rls@%3cdomainName>> in the
file.
Create subscribe using the service uri in the request line method
using SIPp or some SIP client program. (please refer to rls_crash.pcap
file).
Kamailio crashes as soon as the subscribe is being processed.
For the convenience of testing, I had disabled authentication for the
Subscribe method.
Thank you for looking into this Daniel,
Gnaneshwar Gatla | InTouch Health | Software Developer
6330 Hollister Ave. Goleta CA, 93117 | P: 805.562.8686 ext: 199
*From:*Daniel-Constantin Mierla [mailto:miconda@gmail.com]
*Sent:* Friday, April 27, 2012 6:21 AM
*To:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
Users Mailing List
*Cc:* Gnaneshwar Gatla
*Subject:* Re: [SR-Users] kamailio Crashes with rls module
Hello,
can you send the backtrace? according to the logs, there is a core file:
Apr 26 21:00:42 SIPDev /usr/local/sbin/kamailio[14369]: ALERT:<core> [main.c:751]:
child process 14374 exited by a signal 11
Apr 26 21:00:42 SIPDev /usr/local/sbin/kamailio[14369]: ALERT:<core> [main.c:754]:
core was generated
Can it be reproduced? Or just happened randomly.
Btw, sending such large files (the log in this case, over 15MB) as
attachment is not really recommended. Maybe you can host it on an
website for download or send parts of the log, the last messages
before the core message. Also, compressing it in such case is better.
Keep memlog and memdbg higher than debug, all the memory operations
are not relevant unless they are required by a developer for
troubleshooting.
Cheers,
Daniel
On 4/26/12 11:15 PM, Gnaneshwar Gatla wrote:
Oppsie.. forgot to attach the document.
Gnaneshwar Gatla | InTouch Health | Software Developer
6330 Hollister Ave. Goleta CA, 93117 | P: 805.562.8686 ext: 199
*From:*Gnaneshwar Gatla
*Sent:* Thursday, April 26, 2012 2:14 PM
*To:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
Users Mailing List
*Subject:* kamailio Crashes with rls module
Hello,
I’m experimenting the usage of rls module with Kamailio. I have been
able to successfully update xcap documents on Kamailio XCAP server.
I have tried to use SIPp to get a NOTIFY for subscribing a rls-service
list.
Kamailio does get the xml from the xcap table and tries to parse it
and crashes. I’m not sure if this is because the format of the XML, I
derived the xml format from the RFC 4662 and 4826.
I have attached the Kamailio log. I need help with this.
Any help is appreciated, thank you very much.
Gnaneshwar Gatla | InTouch Health | Software Developer
6330 Hollister Ave. Goleta CA, 93117 | P: 805.562.8686 ext: 199
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -http://www.asipto.com
http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda>
-http://www.linkedin.com/in/miconda