[asterisk-bugs] [JIRA] (ASTERISK-29154) SIGABRT

Wed Nov 11 05:01:15 CST 2020

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252708#comment-252708 ] 

Asterisk Team commented on ASTERISK-29154:
------------------------------------------

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> SIGABRT 
> --------
>
>                 Key: ASTERISK-29154
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29154
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 13.37.0
>         Environment: Centos 7, Asterisk 13.37.0 
>            Reporter: Josep B
>              Labels: webrtc
>
> Hi,
> We are using centos7, asterisk 13.37.0 with pjsip 2.10 bundled, using webrtc transport with ‘rel100‘ activated.
> We get a SIGABRT crash:
> Thread 1 (Thread 0x7f59e6487700 (LWP 7700)):
> #0  0x00007f5ac0cb1277 in raise () from /usr/lib64/libc.so.6
> #1  0x00007f5ac0cb2968 in abort () from /usr/lib64/libc.so.6
> #2  0x00007f5ac0cf3d37 in __libc_message () from /usr/lib64/libc.so.6
> #3  0x00007f5ac0cfa5e4 in malloc_printerr () from /usr/lib64/libc.so.6
> #4  0x00007f5ac0cfdd00 in _int_malloc () from /usr/lib64/libc.so.6
> #5  0x00007f5ac0d012c4 in calloc () from /usr/lib64/libc.so.6
> #6  0x00000000005d85d2 in _ast_calloc (func=0x659eb0 <__PRETTY_FUNCTION__.9350> "__ast_string_field_init", lineno=209, file=0x659e38 "stringfields.c", len=184, num=1) at /usr/src/asterisk-13.37.0/include/asterisk/utils.h:603
> #7  __ast_string_field_init (mgr=mgr at entry=0x7f5aa803f350, pool_head=pool_head at entry=0x7f5aa803f290, needed=needed at entry=1024, file=file at entry=0x658ad5 "stasis_channels.c", lineno=lineno at entry=244, func=func at entry=0x659210 <__PRETTY_FUNCTION__.16517> "ast_channel_snapshot_create") at stringfields.c:209
> #8  0x00000000005cada7 in ast_channel_snapshot_create (chan=chan at entry=0x7f5a9c004f88) at stasis_channels.c:244
> #9  0x00000000005cdd38 in ast_channel_publish_snapshot (chan=chan at entry=0x7f5a9c004f88) at stasis_channels.c:776
> #10 0x000000000058152c in pbx_exec (c=c at entry=0x7f5a9c004f88, app=app at entry=0x3258140, data=data at entry=0x7f59e6479de0 "0?Set(CDR(recordingfile)=)") at pbx_app.c:489
> #11 0x0000000000575f30 in pbx_extension_helper (c=c at entry=0x7f5a9c004f88, context=0x7f5a9c005940 "macro-hangupcall", exten=exten at entry=0x7f5a9c005990 "s", priority=priority at entry=3, label=label at entry=0x0, callerid=callerid at entry=0x7f5a440757f0 "649226018", action=action at entry=E_SPAWN, found=0x7f59e647ffa0, combined_find_spawn=combined_find_spawn at entry=1, con=0x0) at pbx.c:2907
> #12 0x0000000000577a73 in ast_spawn_extension (c=c at entry=0x7f5a9c004f88, context=<optimized out>, exten=exten at entry=0x7f5a9c005990 "s", priority=priority at entry=3, callerid=callerid at entry=0x7f5a440757f0 "649226018", found=<optimized out>, combined_find_spawn=combined_find_spawn at entry=1) at pbx.c:4160
> #13 0x00007f5a08941cb7 in _macro_exec (chan=<optimized out>, data=<optimized out>, exclusive=<optimized out>) at app_macro.c:450
> #14 0x0000000000581579 in pbx_exec (c=c at entry=0x7f5a9c004f88, app=app at entry=0x3791630, data=data at entry=0x7f59e6480a40 "hangupcall") at pbx_app.c:494
> #15 0x0000000000575f30 in pbx_extension_helper (c=c at entry=0x7f5a9c004f88, context=0x7f5a9c005940 "macro-hangupcall", exten=exten at entry=0x7f5a9c005990 "s", priority=priority at entry=1, label=label at entry=0x0, callerid=callerid at entry=0x7f5a440757f0 "649226018", action=action at entry=E_SPAWN, found=found at entry=0x7f59e6486ae0, combined_find_spawn=combined_find_spawn at entry=1, con=0x0) at pbx.c:2907
> #16 0x0000000000577bf4 in ast_spawn_extension (combined_find_spawn=1, found=0x7f59e6486ae0, callerid=0x7f5a440757f0 "649226018", priority=1, exten=0x7f5a9c005990 "s", context=<optimized out>, c=0x7f5a9c004f88) at pbx.c:4160
> #17 ast_pbx_h_exten_run (chan=chan at entry=0x7f5a9c004f88, context=<optimized out>) at pbx.c:4190
> #18 0x0000000000579199 in __ast_pbx_run (c=c at entry=0x7f5a9c004f88, args=args at entry=0x0) at pbx.c:4554
> #19 0x000000000057955b in pbx_thread (data=data at entry=0x7f5a9c004f88) at pbx.c:4661
> #20 0x00000000005efc4a in dummy_start (data=<optimized out>) at utils.c:1239
> #21 0x00007f5ac19d6e25 in start_thread () from /usr/lib64/libpthread.so.0
> #22 0x00007f5ac0d79bad in clone () from /usr/lib64/libc.so.6
> We attach additional information.
> ¿Does anyone know if it’s a known issue?
> We can colaborate testing or getting additional information.

--
This message was sent by Atlassian JIRA
(v6.2#6252)