Bugs item #27666, was opened at 2010-01-06 15:31
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=27666&group_id=494

Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Aaron Turner (synfinatic)
>Assigned to: Charlie Savage (cfis)
Summary: segfault under linux/x86 and ruby 1.9.1p376

Initial Comment:
This is a repeatable crash although the backtrace tends to be different 
occasionally.   I've attached a unit test of the issue (tends to happen on the 
21st request) and some additional backtraces.  I also know this issue occurs 
with older ruby 1.9.1 versions.

/usr/lib/ruby1.9/1.9.1/webrick/httprequest.rb:74: [BUG] Segmentation fault
ruby 1.9.1p376 (2009-12-07 revision 26041) [i386-linux]

-- control frame ----------
c:0007 p:0196 s:0030 b:0030 l:000029 d:000029 METHOD 
/usr/lib/ruby1.9/1.9.1/webrick/httprequest.rb:74
c:0006 p:---- s:0026 b:0026 l:000025 d:000025 FINISH
c:0005 p:---- s:0024 b:0024 l:000023 d:000023 CFUNC  :new
c:0004 p:0044 s:0020 b:0020 l:000019 d:000019 METHOD 
/usr/lib/ruby1.9/1.9.1/webrick/httpserver.rb:46
c:0003 p:0123 s:0009 b:0009 l:0019ec d:000008 BLOCK  
/usr/lib/ruby1.9/1.9.1/webrick/server.rb:183
c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH
c:0001 p:---- s:0002 b:0002 l:000001 d:000001 TOP   
---------------------------
-- Ruby level backtrace information-----------------------------------------
/usr/lib/ruby1.9/1.9.1/webrick/httprequest.rb:74:in `initialize'
/usr/lib/ruby1.9/1.9.1/webrick/httpserver.rb:46:in `new'
/usr/lib/ruby1.9/1.9.1/webrick/httpserver.rb:46:in `run'
/usr/lib/ruby1.9/1.9.1/webrick/server.rb:183:iart_thread'

-- C level backtrace information -------------------------------------------
0x3547be /usr/lib/libruby1.9.so.1.9(rb_vm_bugreport+0x3e) [0x3547be]
0x26fa5c /usr/lib/libruby1.9.so.1.9 [0x26fa5c]
0x26faca /usr/lib/libruby1.9.so.1.9(rb_bug+0x3a) [0x26faca]
0x2fd930 /usr/lib/libruby1.9.so.1.9 [0x2fd930]
0x11c890 /lib/tls/libpthread.so.0 [0x11c890]
0x414d30 /lib/tls/libc.so.6 [0x414d30]
0x41533a /lib/tls/libc.so.6(__libc_free+0x8a) [0x41533a]
0x26daed3 /usr/lib/libxml2.so.2(xmlDictFree+0x135) [0x26daed3]
0x263a7c4 /usr/lib/libxml2.so.2(xmlFreeDoc+0x19d) [0x263a7c4]
0x63edd3 
/usr/lib/ruby1.9/gems/1.9.1/gems/libxml-ruby-1.1.3/lib/libxml_ruby.so(rxml_document_free+0x23)
 [0x63edd3]
0x283ffc /usr/lib/libruby1.9.so.1.9 [0x283ffc]
0x28412f /usr/lib/libruby1.9.so.1.9 [0x28412f]
0x2841ae /usr/lib/libruby1.9.so.1.9 [0x2841ae]
0x3582f7 /usr/lib/libruby1.9.so.1.9 [0x3582f7]
0x34b189 /usr/lib/libruby1.9.so.1.9 [0x34b189]
0x34b89f /usr/lib/libruby1.9.so.1.9 [0x34b89f]
0x34d06e /usr/lib/libruby1.9.so.1.9 [0x34d06e]
0x34e0d0 /usr/lib/libruby1.9.so.1.9(rb_funcall2+0x120) [0x34e0d0]
0x274ec1 /usr/lib/libruby1.9.so.1.9(rb_obj_call_init+0x51) [0x274ec1]
0x2a900a /usr/lib/libruby1.9.so.1.9(rb_class_new_instance+0x3a) [0x2a900a]
0x34219e /usr/lib/libruby1.9.so.1.9 [0x34219e]
0x34efaf /usr/lib/libruby1.9.so.1.9 [0x34efaf]
0x3461df /usr/lib/libruby1.9.so.1.9 [0x3461df]
0x34b89f /usr/lib/libruby1.9.so.1.9 [0x34b89f]
0x34bed2 /usr/lib/libruby1.9.so.1.9 [0x34bed2]
0x34c4a6 /usr/lib/libruby1.9.so.1.9(rb_vm_invoke_proc+0xa6) [0x34c4a6]
0x3599cb /usr/lib/libruby1.9.so.1.9 [0x3599cb]
0x359b51 /usr/lib/libruby1.9.so.1.9 [0x359b51]
0x116371 /lib/tls/libpthread.so.0 [0x116371]
0x47affe /lib/tls/libc.so.6(__clone+0x5e) [0x47affe]

[NOTE]
You may encounter a bug of Ruby interpreter. Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html

Aborted

----------------------------------------------------------------------

>Comment By: Charlie Savage (cfis)
Date: 2011-04-22 22:39

Message:
Hi Aaron,

Sorry this wasn't attended to last year, but just to let you know the latest 
version of libxml-ruby runs your test script without an issues for all 100 
iterations.

Thanks - Charlie

----------------------------------------------------------------------

Comment By: Aaron Turner (synfinatic)
Date: 2010-01-12 12:31

Message:
I was hoping to get an update on this ticket: is someone looking at this?  Do I 
need to provide any more information?  My project is currently at a standstill 
and I either need to figure out a fix or rewrite my code to use a different XML 
parser.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=27666&group_id=494
_______________________________________________
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel

Reply via email to