[Home]

Summary:ASTERISK-26290: User login - double free or corruption (out)
Reporter:David Wilson (dcdata)Labels:
Date Opened:2016-08-11 14:42:45Date Closed:2016-08-11 16:16:53
Priority:CriticalRegression?
Status:Closed/CompleteComponents:Core/PBX
Versions:11.23.0 Frequency of
Occurrence		Frequent
Related
Issues:
duplicatesASTERISK-25706 pbx: Abort asterisk on features reload (handle_hint_change)
Environment:FreePBX - SHMZ release 6.6 2.6.32-431.el6.x86_64 Attachments:( 0) asterisk-log.txt
( 1) gdb.txt
Description:Good day,

Please may I ask for your assistance with the following?

Please excuse me if this should have been posted to the FreePBX issues platform, but from what I understand so far, it appears to be an Asterisk issue?

We run a system that uses FreePBX's Device and User mode.

When a user logs in from a SIP handset (Yealink T20P) using FreePBX's "user_login_out.agi" AGI script, Asterisk exits with the following error:
*** glibc detected *** /usr/sbin/asterisk: double free or corruption (out): 0x00007fc138f75cd0 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x75f4e)[0x7fc13c3a9f4e]
/lib64/libc.so.6(+0x78cf0)[0x7fc13c3accf0]
/usr/sbin/asterisk[0x5377ac]
/usr/sbin/asterisk[0x586590]
/usr/sbin/asterisk[0x598c80]
/lib64/libpthread.so.0(+0x7aa1)[0x7fc13ae4faa1]
/lib64/libc.so.6(clone+0x6d)[0x7fc13c41c93d]

Please see "asterisk-log.txt" for the last couple lines of logging output from Asterisk as Asterisk exits.

Please also see the "gdb.txt" log attached for gdb output from the automatically dumped core file.

Thank you in advance!

Kind regards,
David.








Comments:By: Asterisk Team (asteriskteam) 2016-08-11 14:42:46.273-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) 2016-08-11 15:16:37.896-0500

Thanks for the report! In order to maximize efficiency, there are project guidelines for how to report issues. Please read through the Asterisk Issue Guidelines [1]. After reading the guidelines, please clean up this issue so that bug marshals can more easily help you.

In particular:
1. Don't post extensive debug or logs inside the Description or Comment fields.
2. Use the Description field for a description of the issue, referencing *attached* debug with links or notes.
3. Use the Comment fields for discussion regarding the issue.
4. If you need to put a few lines of debug or logs into any field, surround the text with "noformat" tags to help us read it easily.
5. Attach files with a '.txt' extension where possible so that they can be analyzed futher by bug marshals.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines


By: Rusty Newton (rnewton) 2016-08-11 16:18:28.573-0500

Thanks for cleaning it up.  I closed out the issue and linked it to ASTERISK-25706 as it appears to be a duplicate of ASTERISK-25706 . Check out that issue for more details and you may want to try their patch and comment to let them know you are getting the same issue.