[PROTON-1282] Seg Fault in Ruby Messenger pn_messenger_free

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.10
• Fix Version/s: proton-0.15.0
• Component/s: ruby-binding
• Environment: RHEL 6, with a MRG-M 3 broker, qpid-proton-c via RPMs, and the ruby binding self compiled from the 0.10 release archive
• Assignee: Alan Conway
• Reporter: Chris Pitman
• Created: 15/Aug/16 19:54
• Updated: 08/Feb/17 19:06
• Resolved: 20/Aug/16 15:27

Description

This is the output we're getting form a ruby process that we recently switched over to using the qpid-proton ruby binding against 0.10. I don't see an issue for this, but do see mentions of other people running into them on the mailing lists: https://mail-archives.apache.org/mod_mbox/qpid-proton/201510.mbox/[e-mail]%3e

/usr/lib64/ruby/gems/1.9.1/gems/qpid_proton-0.3/lib/messenger/messenger.rb:83: [BUG] Segmentation fault
ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-linux]
 
-- control frame ----------
c:0005 p:---- s:0012 b:0012 l:000011 d:000011 CFUNC  :pn_messenger_free
c:0004 p:0034 s:0008 b:0008 l:0003a0 d:000007 BLOCK  /usr/lib64/ruby/gems/1.9.1/gems/qpid_proton-0.3/lib/messenger/messenger.rb:83
c:0003 p:---- s:0006 b:0006 l:000005 d:000005 FINISH
c:0002 p:---- s:0004 b:0004 l:000003 d:000003 CFUNC  :call
c:0001 p:0000 s:0002 b:0002 l:001e38 d:001e38 TOP
---------------------------

-- Ruby level backtrace information ----------------------------------------
./run_test.rb:0:in `call'
/usr/lib64/ruby/gems/1.9.1/gems/qpid_proton-0.3/lib/messenger/messenger.rb:83:in `block in finalize!'
/usr/lib64/ruby/gems/1.9.1/gems/qpid_proton-0.3/lib/messenger/messenger.rb:83:in `pn_messenger_free'
 
-- C level backtrace information -------------------------------------------
/usr/lib64/libruby.so.1.9(rb_vm_bugreport+0x5f) [0x3c2c14ccdf]
/usr/lib64/libruby.so.1.9() [0x3c2c058ad6]
/usr/lib64/libruby.so.1.9(rb_bug+0xb3) [0x3c2c058c43]
/usr/lib64/libruby.so.1.9() [0x3c2c0ed665]
/lib64/libpthread.so.0() [0x3d09c0f790]
 
[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html