[asterisk-bugs] [JIRA] (ASTERISK-22474) res_pjsip / res_pjsip_session assertions and segfault

Corey Farrell (JIRA) noreply at issues.asterisk.org
Thu Sep 5 18:01:03 CDT 2013


Corey Farrell created ASTERISK-22474:
----------------------------------------

             Summary: res_pjsip / res_pjsip_session assertions and segfault
                 Key: ASTERISK-22474
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22474
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Resources/res_pjsip, Resources/res_pjsip_session
    Affects Versions: 12.0.0-alpha2
            Reporter: Corey Farrell


It is relatively easy to cause a crash with res_pjsip.  I've attached numbered modules.conf for each test, and cli.conf for the 3rd test.  gdb-logs where obtained by running:
{noformat}
gdb --batch -ex 'r' -ex 'bt' -ex 'thread apply all bt' -ex 'thread apply all bt full' asterisk 2>&1 | tee gdb-log
{noformat}

# use modules-1.conf.  Causes segfault in ast_threadpool_push due to pool==NULL.
# use modules-2.conf.  Causes assert in pjsip_endpt_unregister_module when attempting to cancel res_pjsip load.
# use modules-3.conf and cli-3.conf.  Causes assert in pjsip_endpt_register_module when loading res_pjsip_session for second time.

Additional note: res_pjsip MODULEINFO lists res_sorcery_config as the only required module.  res_sorcery_astdb and res_sorcery_memory should probably be listed as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list