[asterisk-bugs] [JIRA] (ASTERISK-28649) Segfault: ast_variables_destroy #channel_vars #set_var #sorcery_realtime

[John Bowen (JIRA)]

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

John Bowen commented on ASTERISK-28649:
---------------------------------------

More info:
When logging the values in "pjsip_configuration.set_var_handler" I see the values appear to be identical with both column types: TEXT and VARCHAR. However, when I switch to VARCHAR, a call to set_var_to_str occurs, whereas with TEXT it does not.

 

> Segfault: ast_variables_destroy #channel_vars #set_var #sorcery_realtime
> ------------------------------------------------------------------------
>
>                 Key: ASTERISK-28649
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28649
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_realtime
>    Affects Versions: 16.5.0, 16.6.2
>         Environment: CentOS Linux release 7.6.1810 (Core) 
> 3.10.0-957.27.2.el7.x86_64
> Asterisk build: asterisk-16.6.2
> Alembic Version: 3a094a18e75b
>            Reporter: John Bowen
>         Attachments: core.28564-brief.txt, core.28564-full.txt, core.28564-locks.txt, core.28564-thread1.txt
>
>
> Using sorcery realtime, if the column ps_endpoints.set_var` contains more than 16 characters a segfault occurs during the loading of endpoints. 
> This, however, does not occur when statically defining endpoints in pjsip.conf.
> Reproduce with:
> 1) Create three endpoints (odbc, realtime)
> 2) UPDATE ps_endpoints SET set_var = 'abc=1234567890abc' WHERE id is NOT NULL
> 3) Reload asterisk
> Notes:
> - All 3 endpoints must have channel_vars > 16 characters, the issue is not reproducable if only 2 endpoints have channel_vars > 16 chars
> - This issue was not present in 13.17.2 (using pjsip bundled)
> I'll be posting my findings as I dig into the code, but wanted to make core and other users aware of the issue first.



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