[asterisk-bugs] [JIRA] (ASTERISK-29130) Prometheus Segmentation Fault

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp commented on ASTERISK-29130:
-------------------------------------------

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



> Prometheus Segmentation Fault
> -----------------------------
>
>                 Key: ASTERISK-29130
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29130
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/General
>    Affects Versions: 18.0.0
>         Environment: OS: CentOS 7
> Version: asterisk-18.0.0-rc2.tar.gz
>            Reporter: Francisco Correia
>            Severity: Minor
>
> Prometheus Resource while building metrics response creates segmentation fault during active call on a Stasis Application.
> {noformat}
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Core was generated by `/usr/sbin/asterisk -f -g -C /etc/asterisk/asterisk.conf'.
> Program terminated with signal 11, Segmentation fault.
> #0  bridges_scrape_cb (response=0x7f337c0ccc78) at prometheus/bridges.c:129
> 129				PROMETHEUS_METRIC_SET_LABEL(&bridge_metrics[index], 1, "id", (snapshot->uniqueid));
> {noformat}



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