gmane.comp.lang.ruby.modules.libxml.devel

Version 2.1.0 Released

Charlie Savage — 2011-08-01T04:12:00

Version 2.1.0 of the libxml bindings has been released.  The changelog is:

* Ruby 1.9.3 compatability (Charlie Savage).

* Added XPath expression <-> Ruby value conversion methods (Jens Wille).

* Extracted rxml_xpath_to_value from rxml_xpath_context_find (Jens Wille).

* Adapted rxml_xpath_from_value from Gregoire Lejeune's ruby-xslt
   library, see https://github.com/glejeune/ruby-xslt (Jens Wille).

* Allow calling #find on nodes returned from Reader (Charlie Savage).

* Change document handling in XPath::Context to address segmentation 
fault on
   Ruby Enterprise Edition (Charlie Savage).

* Update gemspec file to work directly with bundler thereby allowing git
   repository to be used as gem (Charlie Savage).

* Support gem buld (Charlie Savage).

* Simplify memory management of attributes namespaces to fix
   segmentation faults that occurred when using Ruby 1.9.3 (Charlie Savage).

Thanks,

Charlie

Version 2.0.7 Released

Charlie Savage — 2011-06-25T06:30:29

Version 2.0.7 has been released.  It includes two changes:

* Fix compile issue on Ruby 1.9.3
* Add in 2 new HTML Parser constants - NODEFDTD and NOIMPLIED.

Thanks,

Charlie

Version 2.0.6 Available

Charlie Savage — 2011-05-24T02:11:02

I just pushed up version 2.0.6.  This release includes one change:

* Fix segfault that sometimes occurred when looking up encodings on 1.9.
   In some cases the Ruby encoding infrastructure was not properly
   initialized (nkriege).

Thanks,

Charlie

Version 2.0.4 Released

Charlie Savage — 2011-05-03T00:23:13

I just pushed up the 2.0.4 release of libxml-ruby.  This release 
includes a fix that allows the libxml-ruby bindings to once again be 
compiled against older versions of libxml2 (specifically earlier that 
1.1.25).

Thanks,

Charlie

[ libxml-Bugs-29140 ] segfaults randomly

2011-05-02T06:30:49

Bugs item #29140, was opened at 2011-04-21 07:46
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=29140&group_id=494

Category: memory
Group: None
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: James Pharaoh (jamespharaoh)
Assigned to: Charlie Savage (cfis)
Summary: segfaults randomly

Initial Comment:
I am getting segfaults pretty regularly in my ruby 1.9.1 webrick application. They are always in a block which is accessing libxml nodes. Here's an example, I can add more as I get them, or provide any other help solving this. I don't really know where to start.

/home/james/projects/zattikka-mandar/mandar/ruby/mandar/console/home.rb:15: [BUG] Segmentation fault
ruby 1.9.2p0 (2010-08-18 revision 29036) [x86_64-linux]

Version 2.0.3 Released

Charlie Savage — 2011-05-02T06:54:05

I just pushed up the next release of libxml-ruby.  It includes one big 
fix and lots of little fixes that cleanup most of the old issues on 
RubyForge and GitHub.

The big fix is supporting the use of libxml-ruby in native background 
Ruby threads.  Previously, the use of libxml-ruby in background threads 
in Ruby 1.9.x and higher would often cause segmentation faults.

And for the little fixes, please see below.

Thanks,

Charlie

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

* The biggest change in this release is supporting the use of 
libxml-ruby in native background Ruby threads.  Previously, the use of 
libxml-ruby in background threads in Ruby 1.9.x and higher would often 
cause segmentation faults.  This has now been fixed (Charlie Savage).

* Update Reader#expand so that returned node correctly remembers its
   encoding in Ruby 1.9.x (zerebubuth).

* Add check to verify a node has not been deleted.  This can happen when
   a ruby variable holds a reference to a child node that gets freed
   when its parent gets freed.  Previously

[ libxml-Bugs-29140 ] segfaults randomly

2011-05-02T06:31:06

Bugs item #29140, was opened at 2011-04-21 07:46
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=29140&group_id=494

Category: memory
Group: None
Resolution: Accepted
Priority: 3
Submitted By: James Pharaoh (jamespharaoh)
Assigned to: Charlie Savage (cfis)
Summary: segfaults randomly

Initial Comment:
I am getting segfaults pretty regularly in my ruby 1.9.1 webrick application. They are always in a block which is accessing libxml nodes. Here's an example, I can add more as I get them, or provide any other help solving this. I don't really know where to start.

/home/james/projects/zattikka-mandar/mandar/ruby/mandar/console/home.rb:15: [BUG] Segmentation fault
ruby 1.9.2p0 (2010-08-18 revision 29036) [x86_64-linux]

[ libxml-Bugs-28101 ] Segmentation Fault whenrunning on Snow Leopard (Mac OS 10.6.3)

2011-05-02T06:30:28

Bugs item #28101, was opened at 2010-04-16 10:22
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=28101&group_id=494

Category: memory
Group: None
Resolution: Accepted
Priority: 3
Submitted By: Matt Young (fireknite)
Assigned to: Charlie Savage (cfis)
Summary: Segmentation Fault when running on Snow Leopard (Mac OS 10.6.3)

Initial Comment:
I've been getting this error:
------------------------------------------------------
[BUG] Segmentation fault
ruby 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0]

Abort trap
------------------------------------------------------

When trying to run code since Apple released an update for Snow Leopard 10.6.2 --> 10.6.3.

Code worked perfectly fine in 10.6.2 on both snow leopard and snow leopard server, but breaks at 10.6.3.


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

Date: 2011-05-02 00:30

Message:
Hi Matt,

I am going to close this issue since I believe it is fixed.  Please reopen on Github if n

[ libxml-Bugs-27977 ] libxml-ruby-1.1.3 failing test

2011-05-02T06:29:49

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

Category: General
Group: None
Resolution: Accepted
Priority: 3
Submitted By: Matthew Kent (mattkent)
Assigned to: Charlie Savage (cfis)
Summary: libxml-ruby-1.1.3 failing test

Initial Comment:
Packaging libxml-ruby for CentOS 5.4 and I'm getting one failing test

  1) Failure:
test_mode(TestReader) [./test/tc_reader.rb:178]:
<3> expected but was
<5>.

289 tests, 1284 assertions, 1 failures, 0 errors

looks like it's still in XML::Reader::MODE_READING mode

This is with

libxml2-2.6.26-2.1.2.8
libxml2-devel-2.6.26-2.1.2.8

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

Date: 2011-05-02 00:29

Message:
Hi Matthew,

I am going to close this issue since I haven't heard back.  Please reopen on Github if needed.  See https://github.com/xml4r/libxml-ruby

Thanks - Charlie

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

[ libxml-Bugs-26672 ] Segmentation fault

2011-05-02T06:28:36

Bugs item #26672, was opened at 2009-07-20 07:06
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=26672&group_id=494

Category: None
Group: None
Resolution: Accepted
Priority: 3
Submitted By: Thomas Preymesser (thopre)
Assigned to: Charlie Savage (cfis)
Summary: Segmentation fault

Initial Comment:
/usr/local/lib/ruby/gems/1.9.1/gems/libxml-ruby-1.1.3/lib/libxml/attributes.rb:6: [BUG] Segmentation fault
ruby 1.9.2dev (2009-07-20 trunk 24213) [i686-linux]

[ libxml-Bugs-26863 ] Libxml::Node#children causessegfault

2011-05-02T06:26:56

Bugs item #26863, was opened at 2009-08-04 22:27
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=26863&group_id=494

Category: None
Group: None
Resolution: Accepted
Priority: 3
Submitted By: Nobody (None)
Assigned to: Charlie Savage (cfis)
Summary: Libxml::Node#children causes segfault

Initial Comment:

The following ruby snippet causes a segmentation fault with ruby 1.8.7 p160 and libxml-ruby 1.1.3. 

###File: libxml_test.rb###
#! /usr/local/bin/ruby

require "rubygems"
require 'xml'
require 'xml/libxml'

def child(e)
  e.children.each do |n| # segfault
    child(n)
  end
end

def make_text(txt)
  return
end

file = File.open("html")
regexp_result = file.read

regexp_rexml_result = XML::Parser.string(regexp_result)
doc = regexp_rexml_result.parse

cnt = 1
loop do
  elem = doc.find("//*")
  elem.each{|e|
    child(e)
  }
  p cnt
  cnt+=1
end

###result###
1
2
3
4
./libxml_test.rb:8: [BUG] Segmentation fault
ruby 1.8.7 (2009-04-08 patchlevel 160) [x86_64-linux]


###trac

[ libxml-Bugs-28662 ] Segfault assigningdocument.root when running in thread

2011-05-02T06:25:00

Bugs item #28662, was opened at 2010-10-21 13:21
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=28662&group_id=494

Category: None
Group: None
Resolution: Accepted
Priority: 3
Submitted By: Alan Gano (alangano)
Assigned to: Charlie Savage (cfis)
Summary: Segfault assigning document.root when running in thread

Initial Comment:
Gentoo x86_64; ruby 1.9.2; libxml2 2.7.7; libxml-ruby 1.1.3 (gem)

------------------------------------------------------
#!/opt/ruby/bin/ruby192 -w

require 'libxml'

t1 = Thread.new {
   100000.times { |i|
      document = LibXML::XML::Document.new
      document.root = LibXML::XML::Node.new('test')
   }
}     

t1.join
------------------------------------------------------


Segfault is avoided if:
- .root assignment is removed
- GC.start is called at end of loop
- not run in thread
- the loop is made to run slower (e.g., printing out i variable)


$ ./aa42
./aa42:8: [BUG] Segmentation fault
ruby 1.9.2p0 (2010-08-18 revision 29036) [x86_64-linu

compile libxml-ruby mannualy

Swetha Nesari — 2011-04-26T16:13:54

Hi,

I am using Rubyinstaller on Windows 7.

I tried installing  libxml-ruby1.1.4 and 2.0.2

1.    using the command gem install libxml-ruby
2.    gem install libxml-ruby --platform=x86-
mingw32

3.   gem install libxml-ruby -v 2.0.2

 and  After that when i give  'bundle install'  , I get this error :

1. Faliling to install libxml-ruby 1.1.4 native extensions

 2.extconfig failure : need zlib

Am I missing something here?

How do you manually compile libxml-ruby for windows?

Rdocs says that  Win32 has all builtin binaries for libxml-ruby and its
dependencies.

Please, I need advice.


Thanks,

Swetha
_______________________________________________
libxml-devel mailing list
libxml-devel< at >rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel

[ libxml-Bugs-27432 ] Segfault during garbagecollection

2011-05-02T06:29:13

Bugs item #27432, was opened at 2009-11-13 11:08
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=27432&group_id=494

Category: memory
Group: v0.5
Resolution: Accepted
Priority: 3
Submitted By: Mat Brown (outoftime)
Assigned to: Charlie Savage (cfis)
Summary: Segfault during garbage collection

Initial Comment:
Tracked down a persistent segfault during big Solr reindexes (using libxml-ruby to build the Solr docs) to libxml-ruby. These operations involve building thousands of XML messages and the segfault generally occurs at an unpredictable time during the operation.

We're linking against libxml2 2.6.32

I hope this is helpful - I'm no C expert - but here is the backtrace from the core dump:

#0  0x00000035c2a30215 in raise () from /lib64/libc.so.6
#1  0x00000035c2a31cc0 in abort () from /lib64/libc.so.6
#2  0x000000000049729c in rb_bug ()
#3  0x000000000047495d in ?? ()
#4  <signal handler called>
#5  0x000000000042f577 in ?? ()
#6  0x000000000042f60f in rb_gc_mark ()
#

[ libxml-Bugs-27848 ] Error#code_to_s givesincosistent answer (sometimes wrong)

2011-04-25T20:13:33

Bugs item #27848, was opened at 2010-02-17 05:52
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=27848&group_id=494

Category: General
Group: None
Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: Jarl Friis (jarl)
Assigned to: Charlie Savage (cfis)
Summary: Error#code_to_s gives incosistent answer (sometimes wrong)

Initial Comment:
Hi.

Version 1.1.3

I experience that LibXML::XML::Error#code_to_s gives answers that varies arbitrary.

If I have a Empty document, the parse will give me a Error object with code 4.
but when I use code_to_s on that object it some times returns "DOCUMENT EMPTY" and sometimes "DTD"

I believe it is because the constants defined in Error are not prefixed (as they are in libxml), hence there are two constants with the same value:

irb(main):004:0> XML::Error.const_get("DTD")
=> 4
irb(main):005:0> XML::Error.const_get("DOCUMENT_EMPTY")
=> 4

Jarl


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

Date: 2011-04

[ libxml-Bugs-27848 ] Error#code_to_s givesincosistent answer (sometimes wrong)

2011-04-25T17:42:51

Bugs item #27848, was opened at 2010-02-17 13:52
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=27848&group_id=494

Category: General
Group: None
Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: Jarl Friis (jarl)
Assigned to: Charlie Savage (cfis)
Summary: Error#code_to_s gives incosistent answer (sometimes wrong)

Initial Comment:
Hi.

Version 1.1.3

I experience that LibXML::XML::Error#code_to_s gives answers that varies arbitrary.

If I have a Empty document, the parse will give me a Error object with code 4.
but when I use code_to_s on that object it some times returns "DOCUMENT EMPTY" and sometimes "DTD"

I believe it is because the constants defined in Error are not prefixed (as they are in libxml), hence there are two constants with the same value:

irb(main):004:0> XML::Error.const_get("DTD")
=> 4
irb(main):005:0> XML::Error.const_get("DOCUMENT_EMPTY")
=> 4

Jarl


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

Date: 2011-04

[ libxml-Bugs-25203 ] Calling find without anamespace core dumps on the second error.

2011-04-23T04:41:54

Bugs item #25203, was opened at 2009-04-06 13:38
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=25203&group_id=494

Category: General
Group: None
Priority: 3
Submitted By: John Gorman (jgorman)
Summary: Calling find without a namespace core dumps on the second error.

Initial Comment:
This programs demonstrates a bug in libxml-ruby-1.1.3
running ruby 1.8.5 (2006-08-25) [i386-linux] on CentOS 5.3.

Calling find without a namespace core dumps on the second error.

See the simple attached program to reproduce the problem.

Thanks!

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

Date: 2011-04-22 22:41

Message:
This has been fixed in the latest release.

Thanks for the report - Charlie

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

Comment By: John Gorman (jgorman)
Date: 2009-04-07 10:52

Message:
Actually, any namespace error of any kind in the same ruby
process will core dump on the second error. Yikes. Kills
rails in a h

[ libxml-Bugs-27977 ] libxml-ruby-1.1.3 failing test

2011-04-23T04:40:57

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

Category: General
Group: None
Status: Open
Priority: 3
Submitted By: Matthew Kent (mattkent)
Summary: libxml-ruby-1.1.3 failing test

Initial Comment:
Packaging libxml-ruby for CentOS 5.4 and I'm getting one failing test

  1) Failure:
test_mode(TestReader) [./test/tc_reader.rb:178]:
<3> expected but was
<5>.

289 tests, 1284 assertions, 1 failures, 0 errors

looks like it's still in XML::Reader::MODE_READING mode

This is with

libxml2-2.6.26-2.1.2.8
libxml2-devel-2.6.26-2.1.2.8

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

Date: 2011-04-22 22:40

Message:
Could you try the latest version?

Thanks - Chalrie

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

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=27977&group_id=494

[ libxml-Bugs-27256 ] LoadError - Symbol not found:_xmlAddChild

2011-04-23T03:47:33

Bugs item #27256, was opened at 2009-10-08 09:14
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=27256&group_id=494

Category: None
Group: None
Status: Open
Priority: 3
Submitted By: Joshua Lippiner (jlippiner)
Summary: LoadError - Symbol not found: _xmlAddChild 

Initial Comment:
My system appears to have 1.1.2 AND 1.1.3 installed.   Im running Snow Leopard.  Also, I cannot uninstall 1.1.2 for whatever reason.

11:11 AM ~/projects/v16 => console
Loading development environment (Rails 2.3.4)
Loading haml-edge gem.
LoadError: dlopen(/Users/jlippiner/.gem/ruby/1.8/gems/libxml-ruby-1.1.3/lib/libxml_ruby.bundle, 9): Symbol not found: _xmlAddChild
  Referenced from: /Users/jlippiner/.gem/ruby/1.8/gems/libxml-ruby-1.1.3/lib/libxml_ruby.bundle
  Expected in: flat namespace
 in /Users/jlippiner/.gem/ruby/1.8/gems/libxml-ruby-1.1.3/lib/libxml_ruby.bundle - /Users/jlippiner/.gem/ruby/1.8/gems/libxml-ruby-1.1.3/lib/libxml_ruby.bundle
from /Users/jlippiner/.gem/ruby/1.8/ge

[ libxml-Bugs-27438 ] libxml-ruby-1.1.3 - Schemavalidation for schema containing xs:any

2011-04-23T05:50:25

Bugs item #27438, was opened at 2009-11-15 22:18
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=27438&group_id=494

Category: General
Group: None
Status: Open
Priority: 3
Submitted By: Sudhindra K (sudhi312)
Summary: libxml-ruby-1.1.3 - Schema validation for schema containing xs:any

Initial Comment:
Hi,

I cannot get the schema validation working for a schema containing <xs:any namespace="##other" /> . From the forum I cam to know that this is a known limitation, considering that this is so frequently used by schema developers can this be fixed?

My question to forum and the reply -- 

---------- Forwarded message ----------
From: Darko Miletic <darko< at >uvcms.com>
Date: Wed, Nov 11, 2009 at 6:50 PM
Subject: Re: [xml] Regarding LibXML Schema validation
To: Sudhindra Kulkarni <kulkarni.sudhi< at >gmail.com>
Cc: xml< at >gnome.org




Sudhindra Kulkarni wrote:


Hi,

I have a problem validating a xml generated from a schema which contains an element having <xs:any namespace="##other"

[ libxml-Bugs-26562 ] Invalid free when using XMLSAX parser

2011-04-23T04:55:41

Bugs item #26562, was opened at 2009-07-08 10:28
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=26562&group_id=494

Category: None
Group: None
Priority: 3
Submitted By: Todd Fisher (taf2)
Summary: Invalid free when using XML SAX parser

Initial Comment:
I'm running a fairly complex script, combination of a few different binaries... right now this is what i know is happening from valgrind:

==11639== Invalid free() / delete / delete[]
==11639==    at 0x4C2433D: free (vg_replace_malloc.c:323)
==11639==    by 0xD5AB4CA: xmlFreeParserCtxt (in /usr/lib64/libxml2.so.2.7.3)
==11639==    by 0x4E77D51: (within /usr/lib64/libruby.so.1.8.6)
==11639==    by 0x4E780E6: ruby_xmalloc (in /usr/lib64/libruby.so.1.8.6)
==11639==    by 0xC69C7BE: alloc_hpricot_struct (hpricot_scan.rl:618)
==11639==    by 0x4E62E00: (within /usr/lib64/libruby.so.1.8.6)
==11639==    by 0x4E62FFC: (within /usr/lib64/libruby.so.1.8.6)
==11639==    by 0x4E63D17: (within /usr/lib64/libruby.so.1.8.6)
==11639==