| Summary: | ASTERISK-19105: [JABBER± Jitsi call cause Asterisk to SEGFAULT | ||
| Reporter: | bb (burton82) | Labels: | |
| Date Opened: | 2011-12-25 10:32:11.000-0600 | Date Closed: | 2012-01-28 11:55:23.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_jabber |
| Versions: | 1.8.8.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Ubuntu LUCID X64 AMD Athlon(tm) II X4 605e | Attachments: | ( 0) gdb.txt |
| Description: | When I call my asterisk server from a gmail account everything is working as it should. Then I tried Jitsi (Opensource Jabber Client) jitsi.org. When I call the Asterisk with Jitsi I get a segfault. dmesg: [765247.305903] asterisk[30974]: segfault at 0 ip 00007fed96084052 sp 00007fed68648288 error 4 in libc-2.11.1.so[7fed96001000+17a000] asterisk: xxx-sv00*CLI> Disconnected from Asterisk server Executing last minute cleanups | ||
| Comments: | By: Michael L. Young (elguero) 2011-12-26 11:20:47.348-0600 Thank you for your bug report. In order to move your issue forward, we require a backtrace[1] from the core file produced after the crash. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then: make install After enabling, reproduce the crash, and then execute the backtrace[1] instructions. When complete, attach that file to this issue report. [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: bb (burton82) 2011-12-26 11:50:50.344-0600 backtrace.. I hope this is working out. By: Matt Jordan (mjordan) 2011-12-27 07:41:13.121-0600 It doesn't look like Asterisk was compiled with DONT_OPTIMIZE. As Michael requested, please compile Asterisk with the DONT_OPTIMIZE flag and produce a backtrace using the instructions he linked. By: Paul Belanger (pabelanger) 2012-01-28 11:55:17.350-0600 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines | ||