[Home]

Summary:ASTERISK-26408: res_rtp_asterisk: Crash when adding ICE candidate and running under PowerEL7
Reporter:Toshaan Bharvani (toshaan)Labels:
Date Opened:2016-09-27 09:00:07Date Closed:2020-01-14 11:14:04.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:Resources/res_rtp_asterisk
Versions:13.11.2 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Hardware : IBM Power S822L Virtualization : PowerEL7 KVM VM OS : PowerEL7Attachments:( 0) backtrace.txt
( 1) backtrace2.txt
( 2) backtrace-threads.txt
Description:Asterisk starts up, show the SIP clients.
When any sip clients tries to call out or in, the asterisk process stops with the error message "+++ killed by SIGSEGV (core dumped) +++"
A gdb backtrace gives me the following error.
#16 0x00003fffb5699884 in .__clone () at ../sysdeps/unix/sysv/linux/powerpc/powerpc64/clone.S:109
Comments:By: Asterisk Team (asteriskteam) 2016-09-27 09:00:08.904-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Asterisk Team (asteriskteam) 2016-09-27 09:00:09.851-0500

The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process.
By: Joshua C. Colp (jcolp) 2016-09-27 09:40:05.384-0500

Thank you for the crash report. However, we need more information to investigate the crash. Please provide:

1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1].
2. Specific steps taken that lead to the crash.
3. All configuration information necesary to reproduce the crash.

Thanks!

[1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace


By: Toshaan Bharvani (toshaan) 2016-09-27 10:06:28.250-0500

backtrace file
By: Toshaan Bharvani (toshaan) 2016-09-27 10:11:28.066-0500

Joshua,

1. Added backtrace file as per Asterisk wiki
2. Add any sip client and dial out to a test number, which says SayUnixTime() or MorseCode() and the crash happens
3. The configuration is a default configuration with additionally 1 sip trunk, 3 sip clients and a dialplan to pickup calls from the trunk by the 3 clients, there are 3 test lines to verify the sip clients work, (a) SayUnixTime() , (b) Morsecode company name , and (c) Milliwat. The crash occurs with any execution.

Thanks,
Toshaan.
By: Joshua C. Colp (jcolp) 2016-09-28 11:38:13.106-0500

Is your Asterisk built with debugging available? There's no line numbers in your backtrace which makes it hard to know exactly what is going on. As well this may be a result of the specific environment you are running under.
By: Toshaan Bharvani (toshaan) 2016-09-30 02:34:57.105-0500

The current build has been rebuild as per the wiki with the following options added : DEBUG_THREADS BETTER_BACKTRACES MALLOC_DEBUG DONT_OPTIMIZE
I have added a new backtrace files : backtrace2.txt and a backtrace-threads.txt
By: Joshua C. Colp (jcolp) 2016-10-04 12:48:29.818-0500

[~toshaan] Unfortunately you are running under a platform that has not been tested I believe by anyone, and I'm not surprised that something has come up. You may need to investigate yourself to try to figure out what is going on as it may take someone quite awhile to look into this.
By: Toshaan Bharvani (toshaan) 2016-10-04 13:39:12.419-0500

Yes, both the hardware and software combinations are new platforms, however if you can put me on the right direction, I might better understand what to look for or at.
By: Rusty Newton (rnewton) 2016-10-06 09:34:29.688-0500

Thanks for the information so far. Please additionally move your description of steps for reproduction to the issue description field and attach the configuration files necessary as well as Asterisk log files (with verbose and debug both turned up to 5 and present in the logs).


By: Asterisk Team (asteriskteam) 2016-10-20 12:00:00.597-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines