[Home]

Summary:ASTERISK-26456: format_cap: Crash when running tests/pbx/call_file_retries_alwaysdelete test
Reporter:Badalian Vyacheslav (slavon)Labels:
Date Opened:2016-10-10 12:54:04Date Closed:2020-01-14 11:13:46.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Branch GIT-13-f809850

[Oct 10 16:39:34] WARNING[831]: asterisk:243 errReceived: Asterisk 127.0.0.1 received error: FRACK!, Failed assertion format != NULL (0) at line 213 in __ast_format_cap_append of format_cap.c


=================================================================
==836==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x000000635961 bp 0x7f68b88ba660 sp 0x7f68b88ba650 T75)
   #0 0x635960 in ast_format_get_codec_id /usr/src/asterisk/main/format.c:365
   #1 0x63cb56 in format_cap_framed_init /usr/src/asterisk/main/format_cap.c:172
   #2 0x63d4e7 in __ast_format_cap_append /usr/src/asterisk/main/format_cap.c:225
   #3 0x7f688e0d702e in new_outgoing /usr/src/asterisk/pbx/pbx_spool.c:161
   #4 0x7f688e0dc56e in scan_service /usr/src/asterisk/pbx/pbx_spool.c:451
   #5 0x7f688e0dd295 in queue_file /usr/src/asterisk/pbx/pbx_spool.c:558
   #6 0x7f688e0de979 in scan_thread /usr/src/asterisk/pbx/pbx_spool.c:801
   #7 0x806794 in dummy_start /usr/src/asterisk/main/utils.c:1235
   #8 0x7f68d41c90a3 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x80a3)
   #9 0x7f68d320362c in clone (/lib/x86_64-linux-gnu/libc.so.6+0xe862c)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /usr/src/asterisk/main/format.c:365 in ast_format_get_codec_id
Thread T75 created by T0 here:
   #0 0x7f68d5d2cdd9 in __interceptor_pthread_create (/usr/local/lib64/libasan.so.3+0x30dd9)
   #1 0x806b9d in ast_pthread_create_stack /usr/src/asterisk/main/utils.c:1288
   #2 0x806d0a in ast_pthread_create_detached_stack /usr/src/asterisk/main/utils.c:1308
   #3 0x7f688e0dec21 in load_module /usr/src/asterisk/pbx/pbx_spool.c:920
   #4 0x67441c in start_resource /usr/src/asterisk/main/loader.c:1026
   #5 0x676574 in load_resource_list /usr/src/asterisk/main/loader.c:1290
   #6 0x677523 in load_modules /usr/src/asterisk/main/loader.c:1451
   #7 0x49444a in asterisk_daemon /usr/src/asterisk/main/asterisk.c:4615
   #8 0x493794 in main /usr/src/asterisk/main/asterisk.c:4372
   #9 0x7f68d313cb44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)

==836==ABORTING
Comments:By: Asterisk Team (asteriskteam) 2016-10-10 12:54:04.720-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: Joshua C. Colp (jcolp) 2016-10-12 07:10:06.005-0500

I've never seen this during any test runs under Jenkins, do you have the console output? Testsuite log? Was Asterisk shutting down at the time?
By: Asterisk Team (asteriskteam) 2016-10-26 12:00:00.585-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