| Summary: | ASTERISK-27302: Segfault grp_lock_acquire while processing endpoint event | ||||||
| Reporter: | Ross Beer (rossbeer) | Labels: | |||||
| Date Opened: | 2017-09-29 10:42:54 | Date Closed: | 2017-09-29 15:18:19 | ||||
| Priority: | Major | Regression? | |||||
| Status: | Closed/Complete | Components: | Channels/chan_pjsip | ||||
| Versions: | GIT | Frequency of Occurrence | Frequent | ||||
| Related Issues: |
| ||||||
| Environment: | Fedora 23 | Attachments: | ( 0) core-asterisk-112464-1506699027-thread1.txt | ||||
| Description: | Segfault while handling endpoint event.
{noformat} #0 0x00007fbbcbe8a651 in grp_lock_acquire (p=0x0) at ../src/pj/lock.c:288 glock = 0x0 lck = 0x7fbbcbe8b0a1 <pj_log_add_indent+30> #1 0x00007fbbcbe8aba8 in pj_grp_lock_acquire (grp_lock=0x0) at ../src/pj/lock.c:478 #2 0x00007fbbcbe0894f in tsx_timer_callback (theap=0x1a72ce0, entry=0x7fbba45ca980) at ../src/pjsip/sip_transaction.c:1188 {noformat} There was no useful information given in the log output. | ||||||
| Comments: | By: Asterisk Team (asteriskteam) 2017-09-29 10:42:56.011-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: Rusty Newton (rnewton) 2017-09-29 15:18:20.040-0500 Closing this out as it looks like a duplicate of ASTERISK-27230 or ASTERISK-27256 | ||||||