| Summary: | ASTERISK-25886: Not checking for NULL INTERNAL_OBJ object, Asterisk crashes | ||
| Reporter: | Nicolas Chapleau (nicchap) | Labels: | |
| Date Opened: | 2016-03-31 14:28:18 | Date Closed: | 2020-01-14 11:13:49.000-0600 |
| Priority: | Major | Regression? | Yes |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | 13.2.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Linux centOS 6.5 | Attachments: | |
| Description: | Linux CentOS 6.5
sangoma A108DE PRI cards Getting : ERROR[30921][C-00004648]: atsobj2.c:116 INTERNAL_OBJ: user_data is NULL From looking at where INTERNAL_OBJ is called, I noticed that on line 339 of astobj2.c (Asterisk 13.2.0) that the obj object returned from INTERNAL_OBJ is not checked for NULL, but still used. This could be causing our crash. I also checked the latest build and this occurs on line 342 of astobj2.c Crashes at least once a week. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-03-31 14:28:19.184-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: Joshua C. Colp (jcolp) 2016-03-31 14:44:31.481-0500 This may be the cause of your crash but is not the actual problem. If it's NULL then something has gone quite wrong. Please provide a backtrace showing this and more information about what is going on at the time. By: Asterisk Team (asteriskteam) 2016-04-15 12:00:01.076-0500 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 | ||