[libxml-devel] Test Errors and Seg fault (08-07-19)

2008-07-19 Thread Trans
$ script/test Loaded suite script/test Started .Entity: line 1: parser error : Opening and ending tag mismatch: foo line 1 and foz ^ Entity: line 1: parser error : Opening and ending ta

Re: [libxml-devel] Test Errors and Seg fault (08-07-19)

2008-07-19 Thread Charlie Savage
1) Failure: test_parse_error(TestParserContext) [./test/tc_parser_context.rb:111]: expected but was . 157 tests, 740 assertions, 1 failures, 0 errors /usr/lib/ruby/1.8/test/unit.rb:278: [BUG] Segmentation fault ruby 1.8.6 (2007-09-24) [x86_64-linux] It looks like the segmentation fault is h

Re: [libxml-devel] Test Errors and Seg fault (08-07-19)

2008-07-19 Thread Sean Chittenden
A "real" solution would involve XPath objects registering themselves with documents, and documents checking them when freed. The reason is that Ruby calls free functions in random order. See discussion here: http://blade.nagaokaut.ac.jp/cgi-bin/vframe.rb/ruby/ruby-core/17725?17500-17840+s

Re: [libxml-devel] Test Errors and Seg fault (08-07-19)

2008-07-19 Thread Charlie Savage
Sean Chittenden wrote: A "real" solution would involve XPath objects registering themselves with documents, and documents checking them when freed. The reason is that Ruby calls free functions in random order. See discussion here: http://blade.nagaokaut.ac.jp/cgi-bin/vframe.rb/ruby/ruby-co

Re: [libxml-devel] Test Errors and Seg fault (08-07-19)

2008-07-19 Thread Trans
On Jul 19, 4:45 pm, Charlie Savage <[EMAIL PROTECTED]> wrote: > They do - that's not the problem.  The problem is that Ruby ignores mark > functions on process shutdown.  In other words, free functions are > called in a random order.  For more details see the above thread. > > I view this as a sh

Re: [libxml-devel] Test Errors and Seg fault (08-07-19)

2008-07-19 Thread Charlie Savage
I'm not skilled enough in this area to know for sure, but my gut feeling is that there must be simpler solution. Unfortunately I don't think so. Nobu suggested a reference counting solution, which I don't think would work, and isn't any simpler. The implementation isn't so horrible, its m