| Summary: | ASTERISK-26120: astobj2.c : Asterisk crash, Segmentation fault | ||
| Reporter: | Willy Romão (willyrgf) | Labels: | |
| Date Opened: | 2016-06-17 08:16:46 | Date Closed: | 2020-01-14 11:13:51.000-0600 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | General |
| Versions: | 11.22.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | CentOS Linux 7 (Core), Linux 3.10.0-327.18.2.el7.x86_64 | Attachments: | ( 0) backtrace_1.txt ( 1) backtrace_2.txt |
| Description: | My asterisk got crash for two weeks in one or two times per day, and after many tests and change versions of the S.O. and asterisk, I decide open issue.
Below is the information requested of the 'Asterisk Issue Guidelines', if you are missing some information, I will add. Sorry for my bad english. Thank you all. ----------------------------- Separate logs: /var/log/messages:Jun 16 11:06:36 kernel: asterisk[4558]: segfault at fffffffffffffffc ip 000000000044c1ee sp 00007f7c0ec56710 error 5 in asterisk (deleted)[400000+221000] /var/log/messages:Jun 16 16:59:03 kernel: asterisk[2310]: segfault at fffffffffffffffc ip 000000000044c1ee sp 00007f7bec165710 error 5 in asterisk[400000+221000] | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-06-17 08:16:47.848-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: Willy Romão (willyrgf) 2016-06-17 08:22:39.577-0500 Generate by: # gdb -se "asterisk" -ex "bt full" -ex "thread apply all bt" --batch -c core > /tmp/backtrace.txt The two files is the two crash different. By: Richard Mudgett (rmudgett) 2016-06-17 10:46:24.935-0500 Those backtraces have no symbolic information to say where the crash happened. The backtraces don't show anything useful. Did you install from source and compile it yourself? Please see [1] for information on what you need to do to get backtraces that have usable information. [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Asterisk Team (asteriskteam) 2016-07-02 12:00:02 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 | ||