| Summary: | ASTERISK-18221: Connecting to my prosody xmpp server crashes res_jabber.so with pkt->from = NULL | ||||
| Reporter: | Ethan Blanton (elb) | Labels: | |||
| Date Opened: | 2011-08-02 21:51:15 | Date Closed: | 2011-10-10 15:11:35 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Resources/res_jabber | ||
| Versions: | 1.8.3 1.8.5.0 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Ubuntu 10.04 32-bit, Prosody 0.6.1 | Attachments: | ( 0) asterisk_res_jabber_crash_fix.diff ( 1) backtrace.txt | ||
| Description: | When connecting to my local Prosody 0.6.1 server, res_jabber.so segfaults attempting to resolve pkt->from on an incoming disco stanza (I believe; I have not tracked the incoming data carefully). This crash occurs at every signin, within seconds of signing in. This affects both asterisk 1.8.3.2 and 1.8.5.0. This may be related to ASTERISK-16203, and is certainly related to (but distinct from) 0008205 on the Mantis tracker. I will attempt to attach a backtrace and patch after creating this bug. | ||||
| Comments: | By: Leif Madsen (lmadsen) 2011-09-20 17:11:27.693-0500 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 (I'm posting the above message because your backtrace is optimized, and we need an unoptimized backtrace made with DONT_OPTIMIZE enabled in menuselect.) By: Paul Belanger (pabelanger) 2011-10-10 15:11:27.925-0500 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 By: Jason Marble (marble) 2012-02-16 19:26:26.935-0600 This issue is still present in 1.8.9.2. The attached asterisk_res_jabber_crash_fix.diff does not resolve this issue. | ||||