| Summary: | ASTERISK-18151: Crash in Asterisk under 64 bit arch after authenticating correctly via Asterisk GUI | ||
| Reporter: | Erin Spiceland (espiceland) | Labels: | |
| Date Opened: | 2011-07-18 22:06:08 | Date Closed: | 2011-07-21 10:26:57 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/HTTP |
| Versions: | 1.8.5.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | x86_64 Linux version 2.6.18-194.11.4.el5 (mockbuild@x86-009.build.bos.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Fri Sep 17 04:57:05 EDT 2010 | Attachments: | ( 0) cli-output.txt |
| Description: | Asterisk crashes after a successful authentication via the Asterisk GUI. Attempting to authenticate with an incorrect password will not cause this crash to occur. I can reproduce this in Asterisk 1.8.5.0 and head of Asterisk 1.8 branch, but not Asterisk 1.10. Enabling MALLOC_DEBUG causes the crash to go away, and disabling it causes the crash to reappear. I attempted to get a backtrace using gdb, but gdb could not find a trace in my core file. Also, testing under valgrind did not produce a crash, but testing again without using valgrind will cause the crash to reappear. | ||
| Comments: | By: Zhang Debo (debo) 2011-07-18 23:01:53.151-0500 Same issue in same environment. I tried both RPM and SVN versions of GUI. It happens when parsing extensions.conf. By: Erin Spiceland (espiceland) 2011-07-21 10:26:57.047-0500 This was fixed in r327950. | ||